>>>>> On Fri, 17 Jan 2014, grozin wrote: > Maybe, a good solution is to introduce a special arch, "noarch", for > such packages (similar to what's done in the rpm world). Then, if a > package is ~noarch, it is automatically considered ~arch for all > arches. Similar for stable. The maintainer should be able to keyword > ~noarch and to stabilize noarch. Comments?
How would you handle dependencies in such a scenario? All dependencies must be keyworded or stable on all architectures, before the package can be keyworded or stabilised on noarch? Ulrich
pgpF0dADhYThd.pgp
Description: PGP signature
