Launchpad itself

PPAs are for multiple packages, but projects contain a single source tree with forks.

Asked by Shannon Freud

I'ld like to delete the sfsectools project to re-instantiate it on a per tool basis since this difference is non-obvious to non-platform designers.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Shannon Freud
Solved:
Last query:
Last reply:
Revision history for this message
Shannon Freud (d-schadenfreude-007) said : 		#1

I'm deleting this question because nobody paid attention to the parent bug report and canonical evidently WANTS people to run child repos instead of doing source tracking as it should be done. Have a nice day.

Revision history for this message
William Grant (wgrant) said : 		#2

I'm not sure what you're talking about. There's no bug report linked to this question, you've not filed any Launchpad bugs, and it's not clear what you mean by "child repos" or "source tracking".

In Launchpad, a project usually tracks bugs, code, etc. for a single codebase. All members of the community around the project can participate in one place. Separately, a PPA provides users with an Ubuntu apt repository, with which the owner can publish arbitrary Ubuntu packages -- packages containing code from many projects, or from just one. The only relationship between projects and PPAs is that a Launchpad user can take code from a Launchpad project and publish it for Ubuntu users in a PPA, either by manually uploading a package containing that code, or by using a Launchpad recipe to directly construct a PPA package from a project's code branches.