Alin Năstac kirjoitti:
Marius Mauch wrote:
Two questions:
- are there more packages that could benefit from this?
None that I know of. However, there might be other similar packages
without a source tarball (slim chance, but quite possible). At first, I
asked upstream to provide such
Marius Mauch 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.
On Tuesday 17 July 2007 09:57:53 Luca Barbato wrote:
Marius Mauch wrote:
Two questions:
- are there more packages that could benefit from this?
ffmpeg, mplayer, libdvdread, mlt...
Finally, this bug could be closed too, since the development in SVN is
proceeded very far, but no versioned
On Tue, 17 Jul 2007 07:25:02 +0300
Alin Năstac [EMAIL PROTECTED] wrote:
Basically I need a pkg_create() that will be executed only in the
context of the upcoming ebuild ${PF}.ebuild create command.
This isn't something that should be done in an ebuild. It's more
suitable to an external script
Alin Năstac wrote:
The upstream doesn't offer a source tarball, so I need to construct
it myself from their svn repository.
If you're creating a live ebuild, there are already existing eclasses
that works from the user's POV.
If your aim is to create an ebuild for a specific version, you might
On Tue, Jul 17, 2007 at 09:41:04AM +0300, Petteri Räty wrote:
Alin Năstac kirjoitti:
Marius Mauch wrote:
Two questions:
- are there more packages that could benefit from this?
None that I know of. However, there might be other similar packages
without a source tarball (slim chance, but
Jan Kundrát wrote:
Alin Năstac wrote:
The upstream doesn't offer a source tarball, so I need to construct
it myself from their svn repository.
If you're creating a live ebuild, there are already existing eclasses
that works from the user's POV.
I'm not speaking about live
Ciaran McCreesh wrote:
On Tue, 17 Jul 2007 07:25:02 +0300
Alin Năstac [EMAIL PROTECTED] wrote:
Basically I need a pkg_create() that will be executed only in the
context of the upcoming ebuild ${PF}.ebuild create command.
This isn't something that should be done in an ebuild. It's more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan Kundrát wrote:
Alin Năstac wrote:
The upstream doesn't offer a source tarball, so I need to construct
it myself from their svn repository.
If your aim is to create an ebuild for a specific version, you might as
well checkout stuff yourself
Luca Barbato wrote:
I'm not sure how many special cases/option would be necessary for such
script, like exclude dir, one tar per dir and so on.
The process of creating the tarball is quite specific to the package in
question, therefore you cannot make an universal function that does that.
Alin Năstac wrote:
Luca Barbato wrote:
I'm not sure how many special cases/option would be necessary for such
script, like exclude dir, one tar per dir and so on.
The process of creating the tarball is quite specific to the package in
question, therefore you cannot make an universal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vlastimil Babka wrote:
I think he wants to do exactly that, but having the code needed for this
right in the ebuild, so it can benefit from varibles like PV and
versionator eclass for converting PV to e.g. CVS tags... I think it's
quite elegant
On Tuesday, 17. July 2007 13:16, Mike Auty wrote:
It also means that if a developer has had to move files around or in
some way create the specific layout of the tarball for the ebuild,
they won't be lost if the dev goes away, or retires, etc. So
attaching the specific package creation code
Luca Barbato wrote:
My idea is to have your overlay with live ebuilds and a tool to make a
release out of it.
All the messy stuff remains in pkg_setup/src_unpack all you need to do
then is to iterate the workdir and make tarballs of what you find there.
Sounds good enough?
Basically you
Alin Năstac wrote:
Luca Barbato wrote:
My idea is to have your overlay with live ebuilds and a tool to make a
release out of it.
All the messy stuff remains in pkg_setup/src_unpack all you need to do
then is to iterate the workdir and make tarballs of what you find there.
Sounds good
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
On Tuesday 17 July 2007, Ciaran McCreesh wrote:
Alin Năstac [EMAIL PROTECTED] wrote:
Basically I need a pkg_create() that will be executed only in the
context of the upcoming ebuild ${PF}.ebuild create command.
This isn't something that should be done in an ebuild. It's more
suitable to an
On Tuesday 17 July 2007, Alin Năstac wrote:
P.S: The name proposed by me isn't exactly right, as Mike already
remarked on the bug. I suggest to use src_create as function name.
Marius proposed src_makedist which is pretty good ... i wonder though if there
may be a better prefix than src_ or
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,
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
Marius Mauch wrote:
Two questions:
- are there more packages that could benefit from this?
None that I know of. However, there might be other similar packages
without a source tarball (slim chance, but quite possible). At first, I
asked upstream to provide such tarball, but I got refused
On Tuesday 17 July 2007, Marius Mauch wrote:
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
22 matches
Mail list logo
