[arch-general] [extra] package depending on [community] package

Doug Newgard scimmia at archlinux.info
Fri Feb 13 05:01:22 UTC 2015


On Fri, 13 Feb 2015 10:31:44 +0800
Oon-Ee Ng <ngoonee.talk at gmail.com> wrote:

> On Thu, Feb 12, 2015 at 9:48 PM, Marko Hauptvogel
> <marko.hauptvogel at googlemail.com> wrote:
> > There is afaik no
> > rule that prevents /extra packages from depending on /community,
> > but the number should be kept small.
> 
> As long as there is no rule (and don't get me wrong, I'm not in favour
> of unnecessary bureaucracy) then there's no issue here. As packages
> from [extra] depend on those in [community] I wonder whether it would
> make sense for TUs and devs to coordinate rebuilds. I understand that
> in the case of [core]/[extra] most devs updating a library just simply
> trigger a pkgrel update for rebuilding since they have the proper
> access rights, but obviously TUs don't for [core]/[extra]. Using
> [community-testing] and [testing] for this purpose also comes down to
> the same issue as I don't think TUs can move packages from [testing].

TUs can create rebuild todo lists the same as devs can. In this case,
it was simply missed. It happens.

Doug


More information about the arch-general mailing list