Santiago Vila dixit:
>Ports that do not even exist yet will definitely need a working gcc-5
>if they ever expect to be released architectures some day.
>
>So the natural thing to do (which I think it is what we have always done,
>but I may be wrong) is to use unstable as their starting point, not stable.
The problem here is ordering.
Assuming you can take an up-to-date unstable and bootstrap another
architecture using cross-compiling (Helmut Grohne does this regularily)
you have no troubles.
But often, people take other distros as starting point, compiling
things peu à peu, using older versions of packages if newer ones
don’t work OOTB as long as they fulfil the B-D, etc. which is all
perfectly valid.
Especially, packages pre-installed in the buildd chroots can be
out of date for quite some time.
But since this discussion is copied to the m68k list, I hope that
everyone upgrades their chroots right now ;)
gn8,
//mirabilos
--
“Having a smoking section in a restaurant is like having
a peeing section in a swimming pool.”
-- Edward Burr
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/pine.bsm.4.64l.1508082232580.8...@herc.mirbsd.org
