| 1 |
Paul de Vrieze wrote: |
| 2 |
> |
| 3 |
> - Please base the update on the latest ebuild in the portage tree, not your |
| 4 |
> own version. This is sometimes a problem with people who submit updates to a |
| 5 |
> package that they made the initial ebuild for. Those ebuilds are often |
| 6 |
> cleaned up, but with new versions you still get the same ebuild as the |
| 7 |
> initial one instead of an edited version of the official ebuild |
| 8 |
> |
| 9 |
> - Please please, do not submit ebuilds for version bumps unless necessary and |
| 10 |
> if necessary tell us what changed. |
| 11 |
|
| 12 |
I've a couple of questions about this. Last night I emerged mplayer and |
| 13 |
noticed that aalib didn't get installed even though I had it in USE. |
| 14 |
Obviously, fixing this is a trivial change to the RDEPEND section of the |
| 15 |
ebuild (aalib is autodetected by mplayer and so no change to $myconf is |
| 16 |
necessary). What's the best way to handle small changes like this? |
| 17 |
Should I just file a bug and state what needs to be done, or should I |
| 18 |
file a bug and attach a diff? Is there a rule of thumb for how large a |
| 19 |
change has to be in order to warrant a diff or ebuild? |
| 20 |
|
| 21 |
-- |
| 22 |
Stephen Martin |
| 23 |
|
| 24 |
PGP/GnuPG key 1024D/8C4FCA5D |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives