Am Samstag, 3. März 2018, 15:39:50 CET schrieb Michał Górny: > > That's not a solution. That's cheap a cheap excuse that works for one > package, for today. It does not solve the generic case, it does not mean > that other members of toolchain or any other team will not end up having > to remember extra rules like 'do not remove this ebuild because X wants > it'.
We need to do that anyway, if only as a service to more technically oriented users. I think we should keep in mind that the corresponding audiences are where we draw our power users and potential developers. This idea for sure applies to toolchain packages and parts of base system. Keeping track of old software we want to keep via, say, a wiki page is the easiest part. As an example, I restored a specific old auto* version because it is required for gcc *development* (not usage). -- Andreas K. Hüttel dilfri...@gentoo.org Gentoo Linux developer (council, toolchain, perl, libreoffice, comrel)
signature.asc
Description: This is a digitally signed message part.
