Video results for: pkg 36More results from video 
dbdvrf #36 Debian Developer's Reference http://packages.debian.org/sid/developers-reference - - add-on to should be put in here. * Why (More) http://packages.debian.org/sid/developers-reference - - add-on to should be put in here. * Why should I want this package? This is related to the above, but not the same (this is a mail user agent; this is cool, fast, interfaces with PGP and LDAP and IMAP, has features X, Y, and Z). * If this package should not be installed directly, but is pulled in by another package, this should be mentioned. * If the package is experimental, or there are other reasons it should not be used, if there are other packages that should be used instead, it should be here as well. * How is this package different from the competition? Is it a better implementation? more features? different features? Why should I choose this package. 6.2.4.**Upstream home page We recommend that you add the URL for the package's home page in the Homepage field of the Source section in debian/control. Adding this information in the package description itself is considered deprecated. 6.2.5.**Version Control System location There are additional fields for the location of the Version Control System in debian/control. 6.2.5.1.**Vcs-Browser Value of this field should be a http:// URL pointing to a web-browsable copy of the Version Control System repository used to maintain the given package, if available. The information is meant to be useful for the final user, willing to browse the latest work done on the package (e.g. when looking for the patch fixing a bug tagged as pending in the bug tracking system). 6.2.5.2.**Vcs-* Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar) , cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn ( Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. In the following example, an instance of the field for a Subversion repository of the vim package is shown. Note how the URL is in the svn:// scheme (instead of svn+ssh: //) and how it points to the trunk/ branch. The use of the Vcs-Browser and Homepage fields described above is also shown. Source: vim Section: editors Priority: optional [snip] Vcs-Svn: svn://svn.debian.org/ svn/pkg-vim/trunk/packages/ vim Vcs-Browser: http:/ /svn.debian.org/wsvn/ pkg-vim/trunk/packages/ vim Homepage: http://www.vim.org 6.3.**Best practices for debian/changelog The following practices supplement the Policy on changelog files . 6.3.1.**Writing useful changelog entries The changelog entry for a package revision documents changes in that revision, and only them. Concentrate on describing significant and user-visible changes that were made since the last version. Focus on what was changed *** who, how and when are usually less important. Having said that, remember to politely attribute people who have provided notable help in making the package (e.g., those who have sent in patches). There's no need to elaborate the trivial and obvious changes. You can also aggregate several changes in one entry. On the other hand, don't be overly terse if you have undertaken a major change. Be especially clear if there are changes that affect the behaviour of the program. For further explanations, use the README.Debian file. Use common English so that the majority of readers can comprehend it. Avoid abbreviations, tech-speak and jargon when explaining changes that close bugs, especially for bugs filed by users that did not strike you as particularly technically savvy. Be polite, don't swear. It is sometimes desirable to prefix changelog entries with the names of the files that were changed. However, there's no need to explicitly list each and every last one of the changed files, especially if the change was small or repetitive. You may use wildcards. When referring to bugs, don't assume anything. Say what the problem was, how it was fixed, and append the closes: #nnnnn string. See Section** 5.8.4, ***When bugs are closed by new uploads* ** for more information. 6.3.2.**Common misconceptions (Less)
Commercial Building in Carlton/waterport NY $235,000 $235000 1750 Oak Orchard Rd, Carlton/waterport, NY 14411 For more details, visit us here: (More) $235000 1750 Oak Orchard Rd, Carlton/waterport, NY 14411 For more details, visit us here: www.nothnagle.com For more information contact: John Devery Email: jdevery@nothnagle.com (585) 392-8888 MLS Number: 927330 Long Established Rest. With Bar, Busy Highway West of Roc. Offered with Real Estate, Equipment & Furnishings. Updated in & Out, New Mechanics, 17'X32' Deck with Ramp, Large Pkg. Lot, 75-Seat Dn. Room 25-Bar & 36-Deck. High Traffic, Marinas, Golf, & Sport Fishing Nearby. Too Much to ... (Less)
apache 1.3.36-mips-reliantunix-5.43.pkg 2007-09-17 - extension: pkg - size: 3 MB
apache 1.3.36-mips-reliantunix-5.43.pkg
Hosted on: http://www.uniontransit.com
monotone-0.36-1.pkg.tar.gz 
2007-12-10 - extension: gz - size: 2 MB
monotone-0.36-1.pkg.tar.gz
Hosted on: http://ftp.ds.karen.hj.se
monotone-0.36-1.pkg.tar.gz 2007-10-11 - extension: gz - size: 2 MB
monotone-0.36-1.pkg.tar.gz
Hosted on: http://ftp.ds.karen.hj.se
