PackagingGuideMerge
6833
Comment:
|
6882
|
Deletions are marked like this. | Additions are marked like this. |
Line 6: | Line 6: |
* General working list: [:CategoryMOTUUbuntuPackagingMerge] | |
Line 41: | Line 42: |
* Proposal: Merge with ["HelpingWithBugs"], ["Bugs/Debian"], ["MOTU/Bugs"] | * Proposal: Merge with ["HelpingWithBugs"], ["Bugs/Debian"] |
Line 53: | Line 54: |
* ["HowToBuildDebianPackagesFromScratch"] * Proposal: merge into ["PackagingGuide/Basic"] * norsetto: I would add specific special sections on python, CLI, Java, etc.? * we can do that, and should link as much to Debian policy information we can -- DanielHolbach2 [[DateTime(2007-10-10T14:01:41Z)]] = DONE = == MOTU stuff == * ["MOTU/Packages/CommonPackagingMistakes/ChangingTheOrigTarball"] * Proposal: make it sound less 'policy'-like * If the policy element is removed, it should be made clear that there is a policy (perhaps as a separate document?) ["EmmetHikory"] * ["MOTU/Packages/CommonPackagingMistakes/DebianCopyright"] * Proposal: should go into ["PackagingGuide/Basic"] * Policy aspects are perhaps better kept out of ["PackagingGuide/Basic"]. As with ["MOTU/Packages/CommonPackagingMistakes/ChangingTheOrigTarball"], perhaps these should be separated (in the case of copyright, perhaps merged with ["NewPackageRequirements"] - ["EmmetHikory"] * ["NewPackageRequirements"] * Proposal: merge into ["PackagingGuide/Basic"] * ["MOTU/Packages/CommonPackagingMistakes"] * ToC * ["MOTU/ReferencePackages"] * Proposal: add to ["PackagingGuide/Basic"] * ["MOTU/Packages/Packaging/Tips"] * patching tips * Proposal: merge into ["MOTU/School/PatchingSources"] * pbuilder * CDBS * Proposal: merge with ["PackagingGuide/Basic"] * Python packaging * Proposal: drop and link to appropriate debian docs * links Debian docs * Proposal: links in PackagingGuide appendix * ["MOTU/School/PatchingSources"] * Proposal: merge into ["PackagingGuide/PatchSystems"] |
|
Line 68: | Line 102: |
* ["MOTU/Packages/Merging"] * explanations, alternative approach, another approach, links, FIXME, merge tips * Fix: needs rigorous pruning and update * Proposal: Own Section * ["MOTU/Packages/Packaging/Kubuntu"] * doc links, default values for default kde packages, patch systems, writing manpages, finding build-depends, building, versioning, .pot files stuff * norsetto: .desktop files and shared mime type differences too? * ACK (also a paragraph why .desktop changes belong into upstream (translations, etc.)) -- DanielHolbach2 [[DateTime(2007-10-10T14:01:41Z)]] * Proposal: lots of pruning, keep Kubuntu related material, maybe manpage stuff too * norsetto: why not adding a Gnome specific section too? Stuff like dh_gconf, shared mime etc. * ACK -- DanielHolbach2 [[DateTime(2007-10-10T14:01:41Z)]] * ["MOTU/Packages/Packaging/Tips"] * patching tips * Proposal: merge into ["MOTU/School/PatchingSources"] * pbuilder * CDBS * Proposal: merge with ["PackagingGuide/Basic"] * Python packaging * Proposal: drop and link to appropriate debian docs * links Debian docs * Proposal: links in PackagingGuide appendix |
|
Line 110: | Line 123: |
* ["MOTU/ReferencePackages"] * Proposal: add to ["PackagingGuide/Basic"] |
* ["MOTU/Packages/Packaging/Kubuntu"] * doc links, default values for default kde packages, patch systems, writing manpages, finding build-depends, building, versioning, .pot files stuff * norsetto: .desktop files and shared mime type differences too? * ACK (also a paragraph why .desktop changes belong into upstream (translations, etc.)) -- DanielHolbach2 [[DateTime(2007-10-10T14:01:41Z)]] * Proposal: lots of pruning, keep Kubuntu related material, maybe manpage stuff too * norsetto: why not adding a Gnome specific section too? Stuff like dh_gconf, shared mime etc. * ACK -- DanielHolbach2 [[DateTime(2007-10-10T14:01:41Z)]] * ["MOTU/School/PackagingMistakes"] * Proposal: merge into ["PackagingGuide/Basic"] |
Line 114: | Line 134: |
* Proposal: add as a new chapter * ["MOTU/School/Merging-and-Syncing"] * merging and syncing |
|
Line 121: | Line 138: |
* ["MOTU/School/PackagingMistakes"] * Proposal: merge into ["PackagingGuide/Basic"] * ["MOTU/School/PatchingSources"] * Proposal: merge into ["PackagingGuide/PatchSystems"] * ["HowToBuildDebianPackagesFromScratch"] * Proposal: merge into ["PackagingGuide/Basic"] * norsetto: I would add specific special sections on python, CLI, Java, etc.? * we can do that, and should link as much to Debian policy information we can -- DanielHolbach2 [[DateTime(2007-10-10T14:01:41Z)]] = DONE = == MOTU stuff == * ["MOTU/Packages/CommonPackagingMistakes/ChangingTheOrigTarball"] * Proposal: make it sound less 'policy'-like * If the policy element is removed, it should be made clear that there is a policy (perhaps as a separate document?) ["EmmetHikory"] * ["MOTU/Packages/CommonPackagingMistakes/DebianCopyright"] * Proposal: should go into ["PackagingGuide/Basic"] * Policy aspects are perhaps better kept out of ["PackagingGuide/Basic"]. As with ["MOTU/Packages/CommonPackagingMistakes/ChangingTheOrigTarball"], perhaps these should be separated (in the case of copyright, perhaps merged with ["NewPackageRequirements"] - ["EmmetHikory"] * ["NewPackageRequirements"] * Proposal: merge into ["PackagingGuide/Basic"] * ["MOTU/Packages/CommonPackagingMistakes"] * ToC |
* ["MOTU/School/Merging-and-Syncing"] * merging and syncing * Proposal: add as a new chapter * ["MOTU/Packages/Merging"] * explanations, alternative approach, another approach, links, FIXME, merge tips * Fix: needs rigorous pruning and update * Proposal: Own Section |
Please add comments, but if you do please add your name next to it.
General
Use ToCs everywhere.
- General working list: [:CategoryMOTUUbuntuPackagingMerge]
Material
Packaging Guide
- ["PackagingGuide/Introduction"]
- explains a few tools.
- Proposal: merge with ["MOTU/Recipes"]
Proposal: explain better every prerequisite - in particular Apt/Dpkg (two subpages??) -- MaurizioMoriconi DateTime(2007-10-10T12:11:52Z)
probably a good idea -- DanielHolbach2 DateTime(2007-10-17T08:00:31Z)
- explains a few tools.
["PackagingGuide/GettingStarted"]
- explains a few development packages.
- Proposal: merge in ["MOTU/Recipes"]
- pbuilder use.
FIX: should refer to pbuilder-dist and PbuilderHowto
REQUEST: should reference sbuild as an alternative - ["EmmetHikory"]
good idea -- DanielHolbach2 DateTime(2007-10-17T08:00:31Z)
- explains a few development packages.
- ["PackagingGuide/Basic"]
packaging from scratch, explanation of most important debian/* files
- Proposal: do introduction, but link to Debian policy counterparts
- dh_make
- FIX: -$(MAKE) -i distclean
- CDBS
["PackagingGuide/PatchSystems"]
- Proposal: Merge in ["MOTU/School/PatchingSources"]
- ["PackagingGuide/Updating"]
- package updates
- Proposal: Merge with ["MOTU/Recipes/PackageUpdate"]
FIX: link to ["FreezeExceptionProcess"], ["SponsorshipProcess"]
- package updates
- ["PackagingGuide/Ubuntu"]
- Update
Proposal: Link from ["UbuntuDevelopment"]
Proposal: Merge with ["UbuntuPackagingChanges"]
- Proposal: explain Sync process and when can be make a sync
- ["PackagingGuide/Bugs"]
Proposal: Merge with ["HelpingWithBugs"], ["Bugs/Debian"]
- ["PackagingGuide/Appendix"]
- links
- Proposal: Merge with ["MOTU/Documentation"]
- chroot docs
- Proposal: Merge with other chroot docs
- dh_make example files
- list of dh_* tools
- Proposal: automatically generate? (using editmoin)
- links
MOTU Stuff
["HowToBuildDebianPackagesFromScratch"]
- Proposal: merge into ["PackagingGuide/Basic"]
- norsetto: I would add specific special sections on python, CLI, Java, etc.?
we can do that, and should link as much to Debian policy information we can -- DanielHolbach2 DateTime(2007-10-10T14:01:41Z)
DONE
MOTU stuff
- ["MOTU/Packages/CommonPackagingMistakes/ChangingTheOrigTarball"]
- Proposal: make it sound less 'policy'-like
If the policy element is removed, it should be made clear that there is a policy (perhaps as a separate document?) ["EmmetHikory"]
- Proposal: make it sound less 'policy'-like
- ["MOTU/Packages/CommonPackagingMistakes/DebianCopyright"]
- Proposal: should go into ["PackagingGuide/Basic"]
Policy aspects are perhaps better kept out of ["PackagingGuide/Basic"]. As with ["MOTU/Packages/CommonPackagingMistakes/ChangingTheOrigTarball"], perhaps these should be separated (in the case of copyright, perhaps merged with ["NewPackageRequirements"] - ["EmmetHikory"]
- Proposal: should go into ["PackagingGuide/Basic"]
- Proposal: merge into ["PackagingGuide/Basic"]
- ["MOTU/Packages/CommonPackagingMistakes"]
- ToC
- ["MOTU/ReferencePackages"]
- Proposal: add to ["PackagingGuide/Basic"]
- ["MOTU/Packages/Packaging/Tips"]
- patching tips
- Proposal: merge into ["MOTU/School/PatchingSources"]
- pbuilder
- CDBS
- Proposal: merge with ["PackagingGuide/Basic"]
- Python packaging
- Proposal: drop and link to appropriate debian docs
- links Debian docs
Proposal: links in PackagingGuide appendix
- patching tips
- ["MOTU/School/PatchingSources"]
Proposal: merge into ["PackagingGuide/PatchSystems"]
- ["MOTU/Packages/DesktopFiles"]
- contains tools (why source code on the wiki?), explanations, working list
["EmmetHikory"]
- This is a merge of ~5 previous pages from last cycle
- no clear home for such small scripts
- working list is essentially a collaborative blacklist
- Fix: Make sure people understand that .desktop files need to go upstream, else we don't get translations for them
This is stated in second paragraph. Alternate text welcome ["EmmetHikory"]
- Fix: needs pruning
No idea, where to put in the PackagingGuide
["EmmetHikory"]
Discussion might be good external to PackagingGuide
- Instructions could be merged with info on .menu files, .man pages, etc. as part of a new page (needs volunteer)
Code could be stuck in a package (or hidden in a wiki attachment & linked)
Blacklist probably belongs as part of MOTU coordination pages, external to PackagingGuide
- contains tools (why source code on the wiki?), explanations, working list
- ["MOTU/Recipes"]
- just a ToC
- Proposal: can go away
- ["MOTU/Recipes/CheckingLibrarySymbols"],
- checking library symbols on updates
- Proposal: add to the end of ["PackagingGuide/Updating"]
- ["MOTU/Recipes/Debdiff"]
- how to debdiff
- norsetto: unless it is somewhere else, I would add interdiff and filterdiff too?
If you want to add that, no complaints here - EXCELLENT -- DanielHolbach2 DateTime(2007-10-10T14:01:41Z)
Proposal: merge into ["PackagingGuide/GettingStarted"]
Recommended practices here should match those on ["MOTU/Contributing"]. Both may need updates - ["EmmetHikory"]
- ["MOTU/Recipes/DebianWatch"]
how to use debian/watch
- Proposal: move to ["PackagingGuide/Basic"]
- ["MOTU/Recipes/PackageUpdate"]
- how to do a package update
Proposal: merge into ["PackagingGuide/GettingStarted"]
- ["MOTU/Recipes/UseBzrAndBzrBuildpackage"]
explanation on how to organise packaging with bzr
- Proposal: new chapter?
- ["MOTU/Packages/Packaging/Kubuntu"]
- doc links, default values for default kde packages, patch systems, writing manpages, finding build-depends, building, versioning, .pot files stuff
- norsetto: .desktop files and shared mime type differences too?
ACK (also a paragraph why .desktop changes belong into upstream (translations, etc.)) -- DanielHolbach2 DateTime(2007-10-10T14:01:41Z)
- Proposal: lots of pruning, keep Kubuntu related material, maybe manpage stuff too
- norsetto: why not adding a Gnome specific section too? Stuff like dh_gconf, shared mime etc.
- ["MOTU/School/PackagingMistakes"]
- Proposal: merge into ["PackagingGuide/Basic"]
- ["MOTU/School/2005-12-10"]
- packaging without debhelper and CDBS
- Proposal: add as a new chapter
- ["MOTU/School/PackagingBasics"]
- School sessions, lots of questions answered
- Proposal: merge into ["PackagingGuide/Basic"]
- ["MOTU/School/Merging-and-Syncing"]
- merging and syncing
- Proposal: add as a new chapter
- ["MOTU/Packages/Merging"]
- explanations, alternative approach, another approach, links, FIXME, merge tips
- Fix: needs rigorous pruning and update
- Proposal: Own Section
Spec/PackagingGuideMerge (last edited 2008-08-12 12:02:09 by i59F73BC8)