dbdvrf #51 Debian Developer's Reference
- Length: 7:30
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - The debian/packages file contains instruction to build packages and there is no need to create any Makefile files. There is possibility to use macro engine similar to the one used in SPECS files from RPM source packages. For more informations see YADA site. A.3.5.**equivs equivs is another package for making packages. It is often suggested for local use if you need to make a package simply to fulfill dependencies. It is also sometimes used when making ``meta-packages'', which are packages whose only purpose is to depend on other packages. A.4.**Package builders The following packages help with the package building process, general driving dpkg-buildpackage as well as handling supportingtasks. A.4.1.**cvs-buildpackage cvs-buildpackage provides the capability to inject or import Debian source packages into a CVS repository, build a Debian package from the CVS repository, and helps in integrating upstream changes into the repository. These utilities provide an infrastructure to facilitate the use of CVS by Debian maintainers. This allows one to keep separate CVS branches of a package for stable, unstable and possibly experimental distributions, along with the other benefits of a version control system. A.4.2.**debootstrap The debootstrap package and script allows you to bootstrap a Debian base system into any part of your filesystem. By base system, we mean the bare minimum of packages required to operate and install the rest of the system. Having a system like this can be useful in many ways. For instance, you can chroot into it if you want to test your build dependencies. Or you can test how your package behaves when installed into a bare base system. Chroot builders use this package; see below. A.4.3.**pbuilder pbuilder constructs a chrooted system, and builds a package inside the chroot. It is very useful to check that a package's build-dependencies are correct, and to be sure that unnecessary and wrong build dependencies will not exist in the resulting package. A related package is pbuilder-uml, which goes even further by doing the build within a User Mode Linux environment.A.4.4.**sbuild sbuild is another automated builder. It can use chrooted environments as well. It can be used stand-alone, or as part of a networked, distributed build environment. As the latter, it is part of the system used by porters to build binary packages for all the available architectures. See Section**5.10.3.3, ***wanna-build*** for more information, and http://buildd.debian.org / to see the system in action. A.5.**Package uploaders The following packages help automate or simplify the process of uploading packages into the official archive. A.5.1.**dupload dupload is a package and a script to automatically upload Debian packages to the Debian archive, to log the upload, and to send mail about the upload of a package. You can configure it for newupload locations or methods. A.5.2.**dput The dput package and script does much the same thing as dupload, but in a different way. It has some features over dupload, such as the ability to check the GnuPG signature and checksums before uploading, and the possibility of running dinstall in dry-run mode after the upload. A.5.3.**dcut The dcut script (part of the package Section* *A.5.2, ***dput*** ) helps in removing files from the ftp upload directory. A.6.**Maintenance automation The following tools help automate different maintenance tasks, from adding changelog entries or signature lines and looking up bugs in Emacs to making use of the newest and official config.sub. A.6.1.**devscripts devscripts is a package containing wrappers and tools which are very helpful for maintaining your Debian packages. Example scripts include debchange and dch, which manipulate your debian/ changelog file from the command-line, and debuild, which is a wrapper around dpkg-buildpackage. The bts utility is also very helpful to update the state of bug reports on the command line. uscan can be used to watch for new upstream versions of your packages. debrsign can be used to remotely sign a package prior to upload, which is nice when the machine you build the package on is different from where your GPG keys are. See the devscripts(1) manual page for a complete list of available scripts. A.6.2.**autotools-dev autotools-dev contains best practices for people who maintain packages which use autoconf and/or automake. Also contains canonical config.sub and config.guess files which are known to work on all Debian ports. A.6.3.**dpkg-repack dpkg-repack creates Debian package file out of a package that has already been installed. If any changes have been made to the package while it was unpacked (e.g., files in /etc were modified), the new package will inherit the changes. This utility can make it easy to copy packages from one computer to another, or to recreate
dbdvrf #44 Debian Developer's Reference
- Length: 7:31
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - is to let dpkg-source -b construct the repackaged tarball from an unpacked directory. 6.7.8.3.**Changing binary files in diff.gz Sometimes it is necessary to change binary files contained in the original tarball, or to add binary files that are not in it. If this is done by simply copying the files into the debianized source tree, dpkg-source will not be able to handle this. On the other hand, according to the guidelines given above, you cannot include such a changed binary file in a repackaged orig.tar.gz. Instead, include the file in the debian directory in uuencoded (or similar) form ^[7] . The file would then be decoded and copied to its place during the build process. Thus the change will be visible quite easy. Some packages use dbs to manage patches to their upstream source, and always create a new orig.tar.gz file that contains the real orig.tar.gz in its toplevel directory. This is questionable with respect to the preference for pristine source. On the other hand, it is easy to modify or add binary files in this case: Just put them into the newly created orig.tar.gz file, besides the real one, and copy them to the right place during the build process. 6.7.9.**Best practices for debug packages A debug package is a package with a name ending in -dbg, that contains additional information that gdb can use. Since Debian binaries are stripped by default, debugging information, including function names and line numbers, is otherwise not available when running gdb on Debian binaries. Debug packages allow users who need this additional debugging information to install it, without bloating a regular system with the information. It is up to a package's maintainer whether to create a debug package or not. Maintainers are encouraged to create debug packages for library packages, since this can aid in debugging many programs linked to a library. In general, debug packages do not need to be added for all programs; doing so would bloat the archive. But if a maintainer finds that users often need a debugging version of a program, it can be worthwhile to make adebug package for it. Programs that are core infrastructure, such as apache and the X server are also good candidates for debug packages. Some debug packages may contain an entire special debugging build of a library or other binary, but most of them can save space and build time by instead containing separated debugging symbols that gdb can find and load on the fly when debugging a program or library. The convention in Debian is to keep these symbols in /usr/lib/debug/ path, where path is the path to the executable or library. For example, debugging symbols for /usr/ bin/foo go in /usr/lib/ debug/usr/bin/foo, and debugging symbols for /usr/lib/libfoo.so.1 go in /usr/lib/debug/ usr/lib/ libfoo.so.1.The debugging symbols can be extracted from an object file using objcopy --only-keep-debug. Then the object file can be stripped, and objcopy --add-gnu-debuglink used to specify the path to the debugging symbol file. objcopy(1) explains in detail how this works. The dh_strip command in debhelper supports creating debug packages, and can take care of using objcopy to separate out the debugging symbols for you. If your package uses debhelper, all you need to do is call dh_strip --dbg-package= libfoo-dbg, and add an entry to debian/ control for the debug package. Note that the Debian package should depend on the package that it provides debugging symbols for, and this dependency should be versioned. For example: Depends: libfoo-dbg (= ${binary:Version}) [5] We cannot prevent upstream authors from changing the tarball they distribute without also incrementing the version number, so there can be no guarantee that a pristine tarball is identical to what upstream currently distributing at any point in time. All that can be expected is that it is identical to something that upstream once did distribute. If a difference arises later (say, if upstream notices that he wasn't using maximal comression in his original distribution and then re-gzip s it), that's just too bad. Since there is no good way to upload a new .orig.tar.gz for the same version, there is not even any point in treating this situation as a bug. [6] As a special exception, if the omission of non-free fileswould lead to the source failing to build without assistance from the Debian diff, it might be appropriate to instead edit the files, omitting only the non-free parts of them, and/or explain the situation in a README.Debian-source file in the root of the source tree. But in that case please also urge the upstream author to make the non-free components easier seperable from the rest of the source. ^[7] The file should have a name that makes it clear which binary file it encodes. Usually, some postfix indicating the encoding should be appended
dbdvrf #39 Debian Developer's Reference
- Length: 7:55
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - Please use gettext-based templates. Install po-debconf on your development system and read its documentation (man po-debconf is a good start). Avoid changing templates too often. Changing templates text induces more work to translators which will get their translation fuzzied. If you plan changes to your original templates, please contact translators. Most active translators are very responsive and getting their work included along with your modified templates will save you additional uploads. If you use gettext-based templates, the translator's name and e-mail addresses are mentioned in the po files headers. The use of the podebconf-report-po from the po-debconf package is highly recommended to warn translators which have incomplete translations and request them for updates. If in doubt, you may also contact the translation team for a given language (debian-l10n-xxxxx@ lists.debian.org), or the [ debian-i18n@lists.debian.org] mailing list. Calls for translations posted to [debian-i18n@ lists.debian.org] with the debian/po/templates.pot file attached or referenced in a URL are encouraged. Be sure to mentions in these calls for new translations which languages you have existing translations for, in order to avoid duplicate work. 6.5.2.3.**Unfuzzy complete translations when correcting typos and spelling When the text of a debconf template is corrected and you are sure that the change does not affect translations, please be kind to translators and unfuzzy their translations. If you don't do so, the whole template will not be translated as long as a translator will send you an update. To unfuzzy translations, you can proceed the following way: 1. Put all incomplete PO files out of the way. You can check the completeness by using (needs the gettext package installed): for i in debian/po/ *po; do echo -n $i: ; msgfmt -o /dev/null --statistics $i; done 2. move all files which report either fuzzy strings to a temporary place. Files which report no fuzzy strings (only translated and untranslated) will be kept in place. 3. now and now only, modify the template for the typos and check again that translation are not impacted (typos, spelling errors, sometimes typographical corrections are usually OK) 4. run debconf-updatepo. This will fuzzy all strings you modified in translations. You can see this by running the above again 5. use the following command: for i in debian/po/ *po; do msgattrib --output-file= $i --clear-fuzzy $i; done 6. move back to debian/ po the files which showed fuzzy strings in the first step 7. run debconf-updatepo again 6.5.2.4.**Do not make assumptions about interfaces Templates text should not make reference to widgets belonging to some debconf interfaces. Sentences like If you answer Yes... have no meaning for users of graphical interfaces which use checkboxes for boolean questions. String templates should also avoid mentioning the default values in their description. First, because this is redundant with thevalues seen by the users. Also, because these default values may be different from the maintainer choices (for instance, when the debconf database was preseeded). More generally speaking, try to avoid referring to user actions. Just give facts. 6.5.2.5.**Do not use first person You should avoid the use of first person ( I will do this... or We recommend...). The computer is not a person and the Debconf templates do not speak for the Debian developers. You should use neutral construction. Those of you who already wrote scientific publications, just write your templates like you would write a scientific paper. However, try using action voice if still possible, like Enable this if ... instead of This can be enabledif .... 6.5.2.6.**Be gender neutral The world is made of men and women. Please use gender-neutral constructions in your writing. 6.5.3.**Templates fields definition This part gives some information which is mostly taken from the debconf-devel(7) manual page. 6.5.3.1.**Type 6.5.3.1.1.**string: Results in a free-form input field that the user can type any string into. 6.5.3.1.2.**password: Prompts the user for a password. Use this with caution; be aware that the password the user enters will be written to debconf's database. You should probably clean that value out of the database as soon as is possible. 6.5.3.1.3.**boolean: A true/false choice. Remember: true/false, not yes/no... 6.5.3.1.4.**select:A choice between one of a number of values. The choices must be specified in a field named 'Choices'. Separate the possible values with commas and spaces, like this: Choices: yes, no, maybe 6.5.3.1.5.**multiselect: Like the select data type, except the user can choose any number of items from the choices list (or chose none of them). 6.5.3.1.6.**note: Rather than being a question
THE REAL Nokia N97 Demonstration Video
- Length: 0:0
- Rating: ( ratings)
- Views:
- Author: Swimm12984
Tags: 2008 android announcement apple conference december foundation g1 iphone macos macosx n97 Nokia phone press release symbian world
Nokia N97 Unveiled and Announced in Barcelone on December 2nd, 2008. Here is the new flagship phone's pilot video from NOKIA WORLD 2008 ConferencePlanned Market Introduction•1st half 2009Category•ExploreInternet•Easy and fast connections to internet services•Easy text input with QWERTY keyboard and touch screen•3.5 inch sliding tilt display •Live personalized home screen with widgets•Up-to-date information via RSS feed•Fully compatible with Oviservices•Browse real web pages•Take pictures and videos and share them immediatelyVideo and TV•Watch high-quality video on the large 3.5 inch 16:9 widescreen•Video playback at 30 fps, for a wide array of formats•Play videos, music and pictures on TV using TV-out•Access internet video feeds through Nokia Video CenterMusic•Enjoy great audio through standard 3.5 mm jack headphones, built-in stereo speakers or Bluetooth technology•Digital music player with support for playlist editing, equalizer and categorized access to your music collection•Search, browse and purchase songs online in Nokia Music Store (for availability, please visit www.music.nokia.com)Maps and Navigation•Nokia Maps with integrated compass and A-GPS receiver•Multimedia city guides and navigation services. Drive: voice guided car navigation, or Walk: pedestrian-optimized turn-by-turn guidance. (Navigation may need to be purchased separately.)Games•World-class game titles with N-Gage Note: Features and services may be offered as upgrade or for purchaseTechnical Profile•System: WCDMA 900/1900/2100 (HSDPA),EGSM 850/900/1800/1900 MHz•User Interface: S60 5th Edition•Dimensions: 117.2 x 55.3 x 15.9 mm*mm (L x W x H) *18.25 mm at camera area•Weight: Approx. 150 g•Display: 3.5 inch TFT with up to 16 million colors HD16:9 widescreen (640x360 pixels)•Battery: Nokia Battery BP-4L, 1500 mAhMedia•Memory: Up to 48GB (32 GB on-board memory,plus 16GB expansion via microSD memory card slot)•Video playback:MPEG-4 / SP and MPEG-4 AVC/H.264,up to 30 fps, up to VGA resolution•RealVideo up to QCIF @ 30 fps•Windows Media (WMV9) up to CIF @ 30 fps•Flash Lite 3.0 / Flash Video in internet browser•Music playback: MP3, AAC, eAAC, eAAC+, WMAMain Camera•Lens: Carl Zeiss Tessar™•Image capture: Up to 5 megapixels (2584 x 1938) JPEG/EXIF (16.7 million/24-bit color)•Video capture: MPEG-4 VGA (640 x 480) at up to 30 fps•Aperture: F2.8•Focal length: 5.4 mm•Flash: Dual LED camera flash and video lightOperating Times•Talk time: Up to 320 min (3G), 400 min (GSM)•Standby time: Up to 400 hrs (3G), 430 hrs (GSM)•Video playback: Up to 4,5 hours (offline mode)•Music playback: Up to 37 hours (offline mode)Connectivity & Data Services•WLAN IEEE 802.11b/g with UPnP support•Micro-USB connector, Hi-Speed USB 2.0•3.5mm stereo headphone plug and TV-out support (PAL/NTSC)•Bluetooth wireless technology 2.0 with A2DP stereo audio, enhanced data rates (EDR)•GPS receiver with support for assisted GPS (A-GPS)©2008 Nokia. All rights reserved. Nokia and Nokia Connecting People are trademarks or registered trademarks of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade names of their respective owners.Specifications are subject to change without notice. The availability of particular products and services may vary by region. Operation times may vary depending on radio access technology used, operator network configuration and usage. Operations, services and some features may be dependent on the network and/or SIM card as well as on the compatibility of the devices used and the content formats supported. Some services are subject to a separate charge.
House for sale in Andratx, Mallorca, Spain
- Length: 2:32
- Rating: ( ratings)
- Views:
- Author: op24upload011
Tags: Apartment Flat Homes Hotel Housing Plot property real-estate Villa
http://www.overseasproperty24.co.uk/en/abroad_properties/atlantik_mittelmeer_sued_europa/203.html?allagents_id=12193&ref_no_p2=2825-PK%2F12193%5Bhofimall%5D&category=HouseHouse (House) for sale in Andratx, Mallorca, Balearic Islands, Mallorca Spain2825-PK Bedrooms: 7 Bathrooms: 6 Living rooms: 6 Constructed area: 500 square meters Land / Plot size: 7,732 square meters Swimming pool: Yes Sea Views: No Price: EUR 1,300,000 (approx GBP 1,094,015) Other: Click on slideshow to vie additional photos of this propertyUnusual opportunity to acquire a large rustic finca property (like a small village or commune) with separate accommodations comprising a total of 7 bedrooms, 6 bathrooms, 3 living rooms, 3 dining rooms, 4 kitchens, minor outbuildings and a pool.Large wooded plot of 7,732 square meters to the foot of a mountain slope just outside the market town of Andratx, dry stone wall borders, beautiful views, private (bumpy) access road ensures privacy, peace and quiet, surrounded by nature.Three separate dwellings each with their own lounge & dining rooms, kitchens, bedrooms & bathrooms. Plus a small studio, various terrace & patio areas, central swimming pool, outside kitchen & barbeque, wash room, laundry room, vivarium, workshop, sauna and massage room.Mains electricity & water + 2 rain water wells, telephone & ADSL lines, some heating.There is still development potential.Thousands of properties at http://www.overseasproperty24.co.ukoverseas property ads
Page: 1 of 8419