[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: synching non-free packages for sarge

On Fri, Aug 13, 2004 at 10:22:54PM -0400, Aaron M. Ucko wrote:
> One issue that we may wish to address before releasing sarge is that
> some arch-dependent non-free packages are behind because the
> autobuilders only touch main and porters only sporadically build them
> for their architectures.

> For instance, until I built bsdgames-nonfree 2.16-1 (aka rogue) for
> several of the outstanding architectures myself just now, it was up to
> date only for my own architecture (i386 :-P) and two others (amd64 and
> powerpc).  It's still behind on arm and mips, and has never been built
> at all on mipsel.  I'd be happy to take care of them too, if I only
> knew where.  (As far as I can tell, I can't log into any arm boxes at
> all, with debussy and rameau down and elara and europa restricted.  As
> for mips(el), casals's motd forbids manual builds and vaughan has no
> chroots, so I seem to be out of luck there as well.  Are there any
> machines I can use for this purpose?  If not, could the relevant
> porters please take care of bsdgames-nonfree?  Thanks.)

I would tend to discourage maintainers of non-free packages from seeking
out additional porter builds at the last minute before release.  If the
packages don't attract enough interest from users of those ports to be
maintained on an ongoing basis, it may be better to have outdated
binaries removed rather than shipping packages that aren't really going
to be supported.

At the very least, soliciting builds for the package on archs where it's
never been built -- and never been missed -- seems like it will just
make it harder for you to maintain the package.  I know most maintainers
I hear talking about mipsel wish they had the *option* of not supporting
the architecture. ;)

Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature

Reply to: