1 |
On Tue, 17 Jul 2007 06:37:43 +0200 |
2 |
Marius Mauch <genone@g.o> wrote: |
3 |
|
4 |
> On Tue, 17 Jul 2007 07:25:02 +0300 |
5 |
> Alin Năstac <mrness@g.o> wrote: |
6 |
> |
7 |
> > I was asked to discuss here a portage enhancement proposed by me |
8 |
> > [1]. |
9 |
> > |
10 |
> > Basically I need a pkg_create() that will be executed only in the |
11 |
> > context of the upcoming "ebuild ${PF}.ebuild create" command. |
12 |
> > |
13 |
> > The package where I need it is app-mobilephone/bitpim. The upstream |
14 |
> > doesn't offer a source tarball, so I need to construct it myself |
15 |
> > from their svn repository. Up till recently, I used some hackery in |
16 |
> > pkg_setup() to create it |
17 |
> > (see the ebuild), but now "ebuild $PF.ebuild setup" verify the |
18 |
> > digest before running pkg_setup(). |
19 |
> > |
20 |
> > [1] http://bugs.gentoo.org/show_bug.cgi?id=185567 |
21 |
> |
22 |
> Two questions: |
23 |
> - are there more packages that could benefit from this? |
24 |
> - is there a particular reason this has to be integrated into the |
25 |
> ebuild and should not be handled by an ordinary script? |
26 |
|
27 |
Sure. Every package with an unversioned upstream tarball that we're |
28 |
forced to mirror a reversioned tarball of, or can't mirror at all. |
29 |
|
30 |
It makes a lot of sense to put this sort of package maintenance and |
31 |
creation information in the same place as the package. |
32 |
|
33 |
But to do it right, we might need a new type of dependency. This will |
34 |
require more research into whether any packages would have a use for it. |
35 |
|
36 |
Thanks, |
37 |
Donnie |