Re: [gentoo-user] patching source
On Wed, 6 Aug 2003 07:23:31 -0700
"Mark Knecht" <[EMAIL PROTECTED]> wrote:
> > this is a bit of overkill don't you think
> >
> > why not just :
> >
> > ebuild file.ebuild unpack
> > cd /var/tmp/portage/packagedir/work/packagedir_unpacked
> > patch source tree
> > ebuild file.ebuild compile
> > ebuild file.ebuild merge
>
> Henti,
>I thought I needed a qmerge at the end of this process to actually
> put
> the application into the live file system?
>
>When should I be using the qmerge option?
qmerge is a step in the merging process.
snippet from the man pages :
qmerge This function installs all the files in the install directory
to the live filesystem. The process works as follows: first, the
pkg_preinst() function (if specified) is run.
Then, the files are merged into the live filesystem, and the installed
files' md5 digests are recorded in
/var/db/pkg/${CATEOGRY}/${PN}-[version-rev]/CONTENTS. After all the
files have been merged, the pkg_postinst() function (if specified) is
executed.
merge Normally, to merge an ebuild, you need to fetch, unpack, compile,
install and qmerge. If you're simply interested in merging the ebuild,
you can use this command, which will
perform all these steps for you, stopping along the way if a particular
step doesn't complete successfully.
So you can use either merge or qmerge ... in this instance qmerge would probably be
better but both should work fine :)
--
Henti Smith
[EMAIL PROTECTED]
Senior Administrator
The Computer-Smith Networking
http://www.tcsn.co.za
--
[EMAIL PROTECTED] mailing list
RE: [gentoo-user] patching source
> > this is a bit of overkill don't you think > > why not just : > > ebuild file.ebuild unpack > cd /var/tmp/portage/packagedir/work/packagedir_unpacked > patch source tree > ebuild file.ebuild compile > ebuild file.ebuild merge Henti, I thought I needed a qmerge at the end of this process to actually put the application into the live file system? When should I be using the qmerge option? Thanks, Mark -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] patching source
Morning! On Wednesday 06 August 2003 06:24, downtime null wrote: > is it possible to download an ebuild package, patch the source, then > build the package? I don't know whether there is an automated solution, but the best I can come up with is the following: 1. Fetch the files: emerge -f 2. Set $PORTDIR_OVERLAY in /etc/make.conf (place for local ebuilds that will not be overwritten by emergy sync) 3. Copy the Ebuild in question and the patch to a place under $PORTDIR_OVERLAY 4. Change the ebuild (add the "epatch" statement, check some ebuild for an example) 5. emerge Step 1 is optional, I think. Also, check the portage docs - I have never done anything with $PORTDIR_OVERLAY, so I don't know what directory will be first searched for an ebuild if it is in both $PORTDIR_OVERLAY and /usr/portage. Possibly you have to give it a unique name. Hope that helps. Cheers, Renat -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] patching source
On Wed, 6 Aug 2003 09:22:32 +0200 Renat Golubchyk <[EMAIL PROTECTED]> wrote: > Morning! > > On Wednesday 06 August 2003 06:24, downtime null wrote: > > is it possible to download an ebuild package, patch the source, then > > build the package? > > I don't know whether there is an automated solution, but the best I can come > up with is the following: > > 1. Fetch the files: > emerge -f > 2. Set $PORTDIR_OVERLAY in /etc/make.conf (place for local ebuilds that will >not be overwritten by emergy sync) > 3. Copy the Ebuild in question and the patch to a place under $PORTDIR_OVERLAY > 4. Change the ebuild (add the "epatch" statement, check some ebuild for an >example) > 5. emerge > > Step 1 is optional, I think. Also, check the portage docs - I have never done > anything with $PORTDIR_OVERLAY, so I don't know what directory will be first > searched for an ebuild if it is in both $PORTDIR_OVERLAY and /usr/portage. > Possibly you have to give it a unique name. this is a bit of overkill don't you think why not just : ebuild file.ebuild unpack cd /var/tmp/portage/packagedir/work/packagedir_unpacked patch source tree ebuild file.ebuild compile ebuild file.ebuild merge This would seem to be the whole point of portage/ebuild setup so that you can have control over the whole process. The above process of duplicating the ebuild and adding your own patches is really only needed if you are submitting a patch to the main ebuild .. but to custom patch just one application the above should work fine. -- Henti Smith [EMAIL PROTECTED] Senior Administrator The Computer-Smith Networking http://www.tcsn.co.za -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] patching source
On Wednesday 06 August 2003 10:18, Henti Smith wrote: > On Wed, 6 Aug 2003 09:22:32 +0200 > > Renat Golubchyk <[EMAIL PROTECTED]> wrote: > > Morning! > > > > On Wednesday 06 August 2003 06:24, downtime null wrote: > > > is it possible to download an ebuild package, patch the source, then > > > build the package? > > > > I don't know whether there is an automated solution, but the best I can > > come up with is the following: > > > > 1. Fetch the files: > > emerge -f > > 2. Set $PORTDIR_OVERLAY in /etc/make.conf (place for local ebuilds that > > will not be overwritten by emergy sync) > > 3. Copy the Ebuild in question and the patch to a place under > > $PORTDIR_OVERLAY 4. Change the ebuild (add the "epatch" statement, check > > some ebuild for an example) > > 5. emerge > > [...] > this is a bit of overkill don't you think > [...] Well, it is an overkill! But it was the first thing that came into my mind. Thanks. Cheers, Renat -- [EMAIL PROTECTED] mailing list
[gentoo-user] patching source
is it possible to download an ebuild package, patch the source, then build the package? what i'm wanting to do is add the sidebar patch for mutt... -- [EMAIL PROTECTED] mailing list
