I keep forgetting to commit new licenses for ebuilds :) Surely it'd make sense for repoman to automatically commit a new license file when the ebuild is committed? Reproducible: Always Steps to Reproduce: 1. 2. 3.
Yep, I agree. This *always* gets people because the situation is "repoman clean" for devs on their development boxes, yet broken for everyone else - frustrating for everyone.
re-assigning to puggy as he is the main repoman guy now.
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
I'll sport a check to make sure the license is in CVS ( ie you ran cvs add ), but I don't think it's proper for repoman to autocommit the license for you.
I disagree with comment #1 ;-) I think it should error out if a developer tries to commit an ebuild with a license that isn't added to the tree but it shouldn't automatically add the license. basically, what comment #4 said.
