| 1 |
On Tuesday 17 July 2007, Ciaran McCreesh wrote: |
| 2 |
> Alin Năstac <mrness@g.o> wrote: |
| 3 |
> > Basically I need a pkg_create() that will be executed only in the |
| 4 |
> > context of the upcoming "ebuild ${PF}.ebuild create" command. |
| 5 |
> |
| 6 |
> This isn't something that should be done in an ebuild. It's more |
| 7 |
> suitable to an external script maintained by the appropriate herd. |
| 8 |
|
| 9 |
except that it makes transition of maintenance of packages from person to |
| 10 |
person, herd to herd, whatever to monkey, a lot easier. not everything has a |
| 11 |
herd and not every herd has a standard (or anything close) as to how these |
| 12 |
things are done. having a useful helper function in an ebuild eases and |
| 13 |
standardizes all of these things. |
| 14 |
|
| 15 |
> There's no point cluttering up the tree with something that is of no |
| 16 |
> use to end users. |
| 17 |
|
| 18 |
incorrect. end users can utilize these functions just as easily as a |
| 19 |
developer to help test a new tarball not yet in the tree. |
| 20 |
-mike |
Archives