On Tue, 17 Jul 2007 06:37:43 +0200 Marius Mauch <[EMAIL PROTECTED]> wrote:
> On Tue, 17 Jul 2007 07:25:02 +0300 > Alin Năstac <[EMAIL PROTECTED]> wrote: > > > I was asked to discuss here a portage enhancement proposed by me > > [1]. > > > > Basically I need a pkg_create() that will be executed only in the > > context of the upcoming "ebuild ${PF}.ebuild create" command. > > > > The package where I need it is app-mobilephone/bitpim. The upstream > > doesn't offer a source tarball, so I need to construct it myself > > from their svn repository. Up till recently, I used some hackery in > > pkg_setup() to create it > > (see the ebuild), but now "ebuild $PF.ebuild setup" verify the > > digest before running pkg_setup(). > > > > [1] http://bugs.gentoo.org/show_bug.cgi?id=185567 > > Two questions: > - are there more packages that could benefit from this? > - is there a particular reason this has to be integrated into the > ebuild and should not be handled by an ordinary script? Sure. Every package with an unversioned upstream tarball that we're forced to mirror a reversioned tarball of, or can't mirror at all. It makes a lot of sense to put this sort of package maintenance and creation information in the same place as the package. But to do it right, we might need a new type of dependency. This will require more research into whether any packages would have a use for it. Thanks, Donnie
signature.asc
Description: PGP signature