Merge ~xnox/ubuntu-seeds/+git/platform:drop-package-maintainance into ~ubuntu-core-dev/ubuntu-seeds/+git/platform:focal
| Status: | Needs review |
|---|---|
| Proposed branch: | ~xnox/ubuntu-seeds/+git/platform:drop-package-maintainance |
| Merge into: | ~ubuntu-core-dev/ubuntu-seeds/+git/platform:focal |
| Diff against target: |
30 lines (+0/-19) 1 file modified
supported-development-common (+0/-19) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Christian Ehrhardt | Disapprove | ||
| Canonical Desktop Team | Pending | ||
| Steve Langasek | Pending | ||
| Ubuntu Core Development Team | Pending | ||
|
Review via email:
|
|||
Commit message
Drop Package Maintainance from supported-
We no longer require build-dependencies to be in main.
Some of the packages listed in Package Maintainance fall under that, i.e. debhelper pkgstriptransal
Other packages are necessory on Ubuntu Developer's machines, i.e. dh-make dput
However, one also really needs ubuntu-dev-tools too, which is universe.
I see a few very obsolete packages in the list which imho we should drop: dupload dselect
Overall, I don't see the benefits or requirements to have these packages in main. Or why we should process MIRs for all the perl packages that devscripts/lintian want to use.
| Christian Ehrhardt (paelzer) wrote | # |
There was an error fetching revisions from git servers. Please try again in a few minutes. If the problem persists, contact Launchpad support.
## Server ##
Just that they are not strictly required to be in main doesn't mean they have to be demoted.
It depends on the level of commitment, everything in main needs to have a owning team and those tools are crucial and really need an owner.
Yes, one could say: "we still look after them" but would this create a third kind of packages "supported like in main but not really"? That would confuse even more it seems.
Also we might have pro-users of Ubuntu and other companies that build their own packages using these tools (quite likely), and they want to know these tools to be in main. For example I'm scared on removing dh-* in that regard.
Also please add a SEG review slot if we have contracts needing some of this to stay in main.
If "MIR effort for dependencies" is the main reason behind this, then maybe there are more fine grained changes e.g. make some of the less common lintian plugins only suggests?
Or mabye a subset could be demoted, but not all of this list as proposed.
I'd be eager to hear what others think, but for now about "Just removing all of-them": Nack