Re: [gentoo-user] Running ebuilds one step at a time
For an answer to your ebuild question and perhaps others... point your browser to: http://gentoo.zhware.net/fuq.html On Fri, 11 Jul 2003 11:13:25 -0700 Mark Knecht <[EMAIL PROTECTED]> wrote: > > > At this point I do the patches or substitute files as required by the > > > developers, then... > > > > > > ebuild compile > > > ebuild install > > > Does this look correct? I had sort of pieced this back together from > > > man ebuild, but I've had a couple of issues over the last few days: > > > > [snip] > > > > You need to specify the ebuild as the second parameter as in the > > previous steps. > > Yes! Just my typing in and forgetting to type that. > > Now that you point out the ebuild package merge command, it appears from the > ebuild man page that maybe the right order for me would be: > > ebuild package fetch > ebuild package unpack > > do my edits > > ebuild package compile > ebuild package install > ebuild package qmerge > > This seems to be what the ebuild merge option is doing. Maybe you are > suggestion that I can still use ebuild merge after the edits, which would > possibly start from the compile step and go forward, but I'm hesitant to > trust that with my limited knowledge of these tools and how to check things > out. I'll give this a try. > > Thanks very much! > > Cheers, > Mark > > > > And note that install will do the "make install" step > > (or whatever the package uses to install) in $DESTDIR, which is at > > /var/tmp/portage//image. To really install the package you need > > the merge step for ebuild, as in "ebuild merge", this > > will copy the content of $DESTDIR to the live filesystem. > > > > Marius > > > > -- > > [EMAIL PROTECTED] mailing list > > > > > > > > -- > [EMAIL PROTECTED] mailing list > -- ** Registered Linux User Number 185956 http://groups.google.com/groups?hl=en&safe=off&group=linux Join me in chat at #linux-users on irc.freenode.net This email account no longers accepts attachments or messages containing html. 2:13pm up 3 days, 11 min, 4 users, load average: 1.60, 1.86, 2.01 -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] Running ebuilds one step at a time
> > At this point I do the patches or substitute files as required by the > > developers, then... > > > > ebuild compile > > ebuild install > > Does this look correct? I had sort of pieced this back together from > > man ebuild, but I've had a couple of issues over the last few days: > > [snip] > > You need to specify the ebuild as the second parameter as in the > previous steps. Yes! Just my typing in and forgetting to type that. Now that you point out the ebuild package merge command, it appears from the ebuild man page that maybe the right order for me would be: ebuild package fetch ebuild package unpack do my edits ebuild package compile ebuild package install ebuild package qmerge This seems to be what the ebuild merge option is doing. Maybe you are suggestion that I can still use ebuild merge after the edits, which would possibly start from the compile step and go forward, but I'm hesitant to trust that with my limited knowledge of these tools and how to check things out. I'll give this a try. Thanks very much! Cheers, Mark > And note that install will do the "make install" step > (or whatever the package uses to install) in $DESTDIR, which is at > /var/tmp/portage//image. To really install the package you need > the merge step for ebuild, as in "ebuild merge", this > will copy the content of $DESTDIR to the live filesystem. > > Marius > > -- > [EMAIL PROTECTED] mailing list > > -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Running ebuilds one step at a time
On Fri, 11 Jul 2003 10:46:48 -0700 Mark Knecht wrote: > I have need once in a while to patch code that emerge won't download > itself. (New CVS from developers) To accomplish this I've been running > the following set of tasks > > ebuild package fetch > ebuild package unpack > ebuild package clean (possibly not required, or wrong?) wrong, clean will wipe out the working directory > At this point I do the patches or substitute files as required by the > developers, then... > > ebuild compile > ebuild install > Does this look correct? I had sort of pieced this back together from > man ebuild, but I've had a couple of issues over the last few days: [snip] You need to specify the ebuild as the second parameter as in the previous steps. And note that install will do the "make install" step (or whatever the package uses to install) in $DESTDIR, which is at /var/tmp/portage//image. To really install the package you need the merge step for ebuild, as in "ebuild merge", this will copy the content of $DESTDIR to the live filesystem. Marius -- [EMAIL PROTECTED] mailing list
[gentoo-user] Running ebuilds one step at a time
Hi, I had asked this about 6 weeks ago, but seem to have misplaced my notes and I'm not finding it in the archives. I'm getting some strange results today. Maybe someone can see what I'm doing wrong. Thanks in advance, and sorry for asking twice. I have need once in a while to patch code that emerge won't download itself. (New CVS from developers) To accomplish this I've been running the following set of tasks ebuild package fetch ebuild package unpack ebuild package clean (possibly not required, or wrong?) At this point I do the patches or substitute files as required by the developers, then... ebuild compile ebuild install Does this look correct? I had sort of pieced this back together from man ebuild, but I've had a couple of issues over the last few days: 1) It seems that for code that's already on my system, if I attempt the patches and compile/install, ebuild often tells me that 'it appears the package is already compiled'. I can get around this (I think!) using all 5 steps, but I do not think the original instructions required me to do this, and logically why should I keep fetching the same things over again? 2) Specifically WRT to the alsa-driver packages, and looking in /lib/modules/2.4.20-gentoo-r2/dernel/sound, I seem to have some old *.o files from June, indicating the install step was not doing what I thought it should, which would be to install today's version. However, I'm starting to get confused, so maybe I'm doing some other stupid thing... Thanks in advance for helping me straighten this out. Cheers, Mark -- [EMAIL PROTECTED] mailing list
