[arch-dev-public] Policy on cross-repo makedepends?

Allan McRae allan at archlinux.org
Fri Jun 25 09:47:48 EDT 2010

On 25/06/10 23:40, Thomas Bächler wrote:
> Am 25.06.2010 14:30, schrieb Pierre Schmitz:
>> On Fri, 25 Jun 2010 22:11:31 +1000, Allan McRae<allan at archlinux.org>
>> wrote:
>>> Do we have a policy on cross-repo makedepends?   i.e. using makedepends
>>> in [extra] for packages in [core].
>>> I ask because I want to bring dejagnu to [extra] so I can do "make
>>> check" for gcc/binutils/etc in their PKGBUILD.  (I currently do it
>>> myself using a local dejagnu package).
>>> I would just go ahead do it, but our integrity check script list
>>> makedepends repo hierarchy amongst the list of issues.
>> I think it's fine to have core packages depending on some of the extra
>> repo at build time.
> We do have core packages with extra or community make/optdepends.

OK.  Should we remove that check from our Integrity Check script?  At 
least [core] packages make/optdepends on [extra].  I am not so sure 
about [community]...


More information about the arch-dev-public mailing list