| 1 |
В Пнд, 31/03/2008 в 06:21 +0000, Duncan пишет: |
| 2 |
> Mike Frysinger <vapier@g.o> posted |
| 3 |
> 200803302039.14615.vapier@g.o, excerpted below, on Sun, 30 Mar |
| 4 |
> 2008 20:39:14 -0400: |
| 5 |
> |
| 6 |
> > there is no package-manager specificness here. it's already completely |
| 7 |
> > doable from a user perspective, just having it in the ebuild makes my |
| 8 |
> > life and users' lives easier. i'm using it in packages that tend to |
| 9 |
> > have a lot of extraneous patchsets associated with them. the random |
| 10 |
> > patches were punted from ebuilds and now it's up to the user to maintain |
| 11 |
> > the feature sets. |
| 12 |
|
| 13 |
> The point here though is that particularly for the glib patch, which has |
| 14 |
> undergone several rounds of testing and looks set for another round or |
| 15 |
> two at least, this user patch infrastructure would sure be nice! |
| 16 |
|
| 17 |
It possible to use /etc/portage/bashrc to have this infrastructure. |
| 18 |
Search mailing list, it was discussed here at least twice, and this is |
| 19 |
example from solar: |
| 20 |
|
| 21 |
http://dev.gentoo.org/~solar/bashrc |
| 22 |
http://dev.gentoo.org/~solar/portage_misc/bashrc.autopatch |
| 23 |
|
| 24 |
There is no need to put such things into ebuild. |
| 25 |
|
| 26 |
-- |
| 27 |
Peter. |
Archives