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
