-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 01/21/2016 02:41 PM, waltd...@waltdnes.org wrote: > On Thu, Jan 21, 2016 at 06:45:20PM +0100, Micha?? Górny wrote >> On Thu, 21 Jan 2016 17:25:02 +0000 Roy Bamford >> <neddyseag...@gentoo.org> wrote: >> >>> There is no point in removing unmaintained but perfectly >>> functional software from the tree. It needs to be both >>> unmaintained and broken. Broken being evidenced by at least one >>> open bug. >> >> That's nonsense. In fact, that's exactly the opposite of what >> should be removed. >> >> If I see a package that clearly doesn't build or otherwise >> simply doesn't work, could not have worked for past 3 years, are >> you forcing me to waste a time reporting a bug to no maintainer >> who could fix it? > > I think you misunderstood Roy. He was speaking about > "unmaintained but perfectly functional software". You're talking > about "a package that clearly doesn't build or otherwise simply > doesn't work, could not have worked for past 3 years". Between > those 2 extremes will be many cases of > doesn't-work-for-me/works-for-me. Who'll be the final arbiter? > > Maybe we should start a "gentoo-ebuilds" mailing list to help > regular users learn the ins and outs of making ebuilds. Once > regular users run a lot of their own ebuilds from their local > overlays, then it would be possible to do draconian pruning of the > "official portage tree", without so adversely affecting regular > users. This would fit in with the mantra of Gentoo being about > freedom of choice. > > E.g. I use Pale Moon, a fork of Firefox. Currently, I have to > build as regular user, su, and copy the binary to /usr/local. You > can see "Walter's excellent adventure" <G> as I learn the build > process at... > https://forum.palemoon.org/viewtopic.php?f=37&t=10002 > > I'd like to have Portage manage the process. The ebuild from > Firefox should serve as a template, because they both use the same > weird Mozilla build setup. The main change should be where the > source is pulled from. >
The idea sounds nice, but there's already the devmanual to cover ebuild development, and now that the gentoo repo is in git, any ebuilds that get treecleaned can be fetched again through history, and users can then add those to their personal overlay(s) and keep the piece if they break. I like the idea of encouraging people to learn good ebuild writing, but who really has the time and skill to teach it? - -- Daniel Campbell - Gentoo Developer OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWoXgPAAoJEAEkDpRQOeFwPvUP/1cOdVx0Mnm2yF6DU9BCXCzn 6LdE4/g05CnkggQkQEPsL6U+oiU/C2wu9nsSSRwrHNKEoIvly/pZEz75+FFoEnF5 RQTltJQi4lyG63bzaHYCx1nzmqAHBVbCBGDPqEC8whV8C8YAufk3SxqocBaIsD5Z IbujCelJNGvRGBPmsIOD38aaVbcyJZFGG+m9nTTJyRQtdFGxfccE/K+xuZMLKFS/ BQkyJdAyvGscRBLAx80o5TgZ+h7BTNW78b8aIubWaeMyqYrvQhdwaDTK7xj0cb5M uxC7fg493PphNLLYY5sL9yHPKtyJzuWhE6r9IXtMSH3b8sTEUU4cXxF4Ep1af+k0 9BafYy+vAxv6fM/3VS8KGcGCwElNrCiNLJYjEdW7mCDRFNQR8cja5IVRF8KGlXD3 33eKUviyPtx9LB5GNS2bZNSayeJbIENr1LsY2gZ4C6nfXUOzsUp7KhM4P4WmFKWV TOn/DbigDQjMa07L0+G+cwvrc2X2QJWG8kstD16iARvaRAnlvlO+HQeSAtO1LWwU 7O44z0eQDxpGO6RZrBDVKNGe8dAaObQT+ueCL/sOHV2Co71Iz8zCu8z75OIhSWWM 8Tu4pa+doFetFLmOkfkcFTxuAjcxJAJomxnLD9rNcdjDtuWF2wxATdWFruFmYPm+ u0/PNb0YQg4Xx5M2qV63 =FxNx -----END PGP SIGNATURE-----
