Differences between revisions 1 and 24 (spanning 23 versions)
Revision 1 as of 2007-09-21 01:29:55
Size: 801
Comment:
Revision 24 as of 2007-10-25 07:05:02
Size: 2225
Comment: Add bug for libapt
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from HomepageFieldTransition
#language en
## I suggest to rename this page "DpkgHomepageFieldTransition" so wiki visitors don't get confused.
## further more, "dpkg" keyword would be page's title, which is good for Google.
Line 5: Line 9:
1.A Add Homepage to Debian Policy Manual. 1.A Implement support in APT frontends and libraries:
 * libapt: Bug:447970
 * Adept Manager: Bug:445649
 * aptitude: Bug:445244
 * synaptic: Bug:445636
 * kpackage: '''done'''
 * packages.debian.org: '''done'''
Line 7: Line 17:
1.B Make lintian stop issuing "I: unknown-field-in-control homepage". 1.B Adapt developer documentation such as the Developer's Reference:
 * Developer's Reference: Bug:445642
Line 9: Line 20:
2.A Implement support in APT frontends. 1.C Add Homepage field to dh-make templates. Bug:445678 (pending in the package SVN repository)
Line 11: Line 22:
2.B Adapt developer documentation such as the Developer's Reference.
2. Make lintian stop issuing "I: unknown-field-in-control homepage". See Bug:444336
Line 15: Line 27:
4. After some time, announce mass bug filing on debian-devel-announce.  * lintian: Bug:339829 and Bug:444336 (merged)
 * linda: Bug:445673
Line 17: Line 30:
5. After some time, proceed to mass bug filing. 4. Add Homepage to Debian Policy Manual as a suggestion:
 * Add an item to "Binary package control files -- DEBIAN/control"
  * Homepage (no "mandatory" mention)
 * Add a level 3 section to "List of fields":
  * Homepage
The upstream project's home page URL. It should preferably
contain and http(s) URL linking to a page describing the upstream
project with access to the project's resources. This is an optional
field.
Line 19: Line 40:
Maybe move this as first step as debian/control fields are indeed described in the policy. The point would be to have a good reference describing that field without making it mandatory.
Line 20: Line 42:
This page is based on [http://lists.debian.org/debian-devel/2007/09/msg00628.htmla message from Christian Perrier to debian-devel] and the resulting thread. 5. After some time, announce mass wishlist bug filing on debian-devel-announce.

6. After some time, proceed to mass wishlist bug filing.

7. After even more time, change the policy manual to should

8. file yet another round of bugs, now non-wishlist.

This page is based on [http://lists.debian.org/debian-devel/2007/09/msg00628.html a message from Christian Perrier to debian-devel] and the resulting thread.
This page amended by Manoj Srivastava and Christian Perrier.

dpkg >= 1.14.6 supports the use of a "Homepage:" field in debian/control. This should replace the Homepage pseudo-field in extended descriptions.

Transition plan

1.A Implement support in APT frontends and libraries:

1.B Adapt developer documentation such as the Developer's Reference:

  • Developer's Reference: 445642

1.C Add Homepage field to dh-make templates. 445678 (pending in the package SVN repository)

2. Make lintian stop issuing "I: unknown-field-in-control homepage". See 444336

3. Make linda and lintian issue a warning to packages including a homepage in their extended description.

4. Add Homepage to Debian Policy Manual as a suggestion:

  • Add an item to "Binary package control files -- DEBIAN/control"
    • Homepage (no "mandatory" mention)
  • Add a level 3 section to "List of fields":
    • Homepage

The upstream project's home page URL. It should preferably contain and http(s) URL linking to a page describing the upstream project with access to the project's resources. This is an optional field.

Maybe move this as first step as debian/control fields are indeed described in the policy. The point would be to have a good reference describing that field without making it mandatory.

5. After some time, announce mass wishlist bug filing on debian-devel-announce.

6. After some time, proceed to mass wishlist bug filing.

7. After even more time, change the policy manual to should

8. file yet another round of bugs, now non-wishlist.

This page is based on [http://lists.debian.org/debian-devel/2007/09/msg00628.html a message from Christian Perrier to debian-devel] and the resulting thread. This page amended by Manoj Srivastava and Christian Perrier.