When to add a new package to comps?
kevin.kofler at chello.at
Fri Jan 17 22:29:41 UTC 2014
Kevin Fenzi wrote:
> On Tue, 14 Jan 2014 17:06:37 +0000 (GMT)
>> Do I first need to wait for the package to make it's way from
>> updates-testing to updates, or can I go ahead and edit comps right
> You should wait until it's in stable for all stable releases, and the
> next day after you build (when it's been in a rawhide compose) for
Uh, why? Comps just ignores unavailable packages, so it should be fine to
add them to comps right away.
> You should also be very careful adding new packages to existing stable
> releases. Typically people don't expect those groups to be changing
Right, new packages should be added to stable releases only as optional, not
as default (or worse, mandatory).
But adding them to some group as optional is a good idea for anything that
end users should get offered for installation (i.e. applications, command-
line tools etc., but not, e.g., libraries). Otherwise, they will not find
the package in Apper when browsing the categories.
More information about the devel