public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philippe Namias <pn@novadeck.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] portage-1.5_pre7
Date: Mon Mar  5 03:41:01 2001	[thread overview]
Message-ID: <01030511303103.05254@cerberus> (raw)
In-Reply-To: <20010301150323.A8832@cvs.gentoo.org>

Hi all,

Just for telling that i just emerge during all the weekend and nearly install 
all the package using emerge. So far with no problem.

But i have a few question :

Why after merging a packages we leave data in /tmp/portage/package_name ?

Is it normal that i can do emerge packgae_name as many time that i want ?

For example if i run it twice emerge on gtk-xemacs i run into trouble telling 
me xemacs can't find the root for data, lib. The only that i found to restore 
gtk-xemacs is to erase the directory  /var/db/packages/apps-editor/gtk-xemacs 
and also /tmp/portage/gtk-xemacs? Any idea?

Thanks
Philippe Namias


On Thursday 01 March 2001 23:03, you wrote:
> Hi all,
>
> I just committed sys-apps/portage-1.5_pre7, a brand new *test*
> version of Portage with recursive merging capability.
>
> Here's how to install it.  First, update your /usr/portage tree.
> Then, do the following:
>
> # cd /etc
> # rm make.conf.eg
> # rm make.defaults.eg
> (if they exist, that is)
>
> # cd /usr/portage/sys-apps/portage
> # ebuild portage-1.5_pre7.ebuild merge
>
> # cd /etc
> # ln -s /usr/portage/profiles/default make.profile
>
> The _beta_ recursive merging capability can be used as follows.
>
> # emerge --pretend foo-1.0.ebuild
>
> This will show you the ebuilds that will be merged to install this
> particular ebuild.  Build deps will be listed first, then runtime
> deps.  There may be duplicates in the runtime deps list; this is
> normal.  The package in question won't be installed twice, since
> this dependency will be satisfied by the time emerge gets to the
> runtime deps.  To do the "real" install:
>
> # emerge foo-1.0.ebuild
>
> :)))
>
> I'm currently using emerge on cvs.gentoo.org, with success.
> It will also work (not with full profile support yet) if you do
> this:
>
> # export ROOT=/mnt/gentoo
> # emerge foo-1.0.ebuild
>
> All build dependencies will be installed to "/" and all runtime
> dependencies will be installed to "/mnt/gentoo" :)))
>
> Enjoy,



  parent reply	other threads:[~2001-03-05 10:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01 15:04 [gentoo-dev] portage-1.5_pre7 drobbins
2001-03-01 18:09 ` Pete Gavin
2001-03-01 18:19   ` Achim Gottinger
2001-03-01 19:11     ` drobbins
2001-03-05  3:41 ` Philippe Namias [this message]
2001-03-05 14:15   ` drobbins
  -- strict thread matches above, loose matches on Subject: below --
2001-03-16 10:16 BoehmeSilvio
2001-03-16 10:30 ` drobbins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01030511303103.05254@cerberus \
    --to=pn@novadeck.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox