Philip Webb <purslow <at> ca.inter.net> writes:
> If anyone else uses Xcdroast to write CDs or DVDs, > I suggest they read Bug 345337 & submit appropriate comments. Tree-cleaners have been very active. If they prose to removed something you like, you have options, like volunteering to proxy-maintain the package, yourself via the proxy-maintainer project:: https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers equery m xcdroast * app-cdr/xcdroast [gentoo] Maintainer: None specified Move it to your own github. Install it locally (usr/local/portage/), along with sources in /usr/local/portage/distfiles. Other ways surely exist. > There seems to be no problem on single-user systems, > but a 6-year-old bug which applies to multi-user systems > is being used as an excuse to remove Xcdroast from the tree. > There was a similar issue with Nethack recently too. Reply to the bug with your evidence, plead your case, in bgo. If no timely responses then discuss it on gentoo-dev. > PS I am not receiving e-alerts re comments added to the bug : > can anyone explain why that mb happening & advise me how to get them ? You probably got listed on the bug to receive updates? What's the bug number? There is a pseudo mandate to removed insecure packages from the tree. It's been discussed on gentoo dev. Some new guideline are being brought forward on tree-cleaning. I have been actively requesting for a well defined pathway for such codes. Read this post and you'll see that one of the devs outlined a process to retrieve old ebuilds from github. It was really easy, via 'the attic', but the attic is not github centric, so those new instructions hopefully will hit the gentoo wiki and get expanded to allow folks to retrieve old codes. Then you have to figure out how YOU are going to maintain those old ebuilds. https://archives.gentoo.org/gentoo-dev/message/305c431c84c39bc74b1077f0b395ce91 hth, James
