-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: move all fetch-restricted ebuilds to extra #13
Comments
I wouldn't say impossible to test - more difficult to test in an automated fashion, but still feasible with smart coding. |
Improved gentoo with emphasis on automated QA and some stuff that makes binary distributions' lives easier, like adelie (but nothing too intrusive). Automated QA is important to avoid tree rot/bitrot. Gentoo has plenty of this in some of its packages. Fetch-restricted ebuilds are not always like java; some of them require you pay for something. vmware-workstation is like this. |
I think an extras repo is a good idea for fetch restricted ebuilds, people have the option if they want a package to install the overlay/repo and get it, and file bugs etc. It just isn't catered for with the Automated QA System, so slower to update/test/etc |
We already have the extras overlay. |
We would need at least a news item. Also anyone with oracle-jdk-bin installed would have to add the extras repo, or the installed package they have would no longer be valid. |
I think we may need to introduce a "no-autotest" flag somewhere then perhaps, as something like java or there are probably others, really should remain part of the 'main tree'. |
Along the lines of #1 I propose we should move fetch-restricted ebuilds to extras, with similar reasoning. Fetch restrictions make packages impossible to test.
The text was updated successfully, but these errors were encountered: