On Sun, 2005-03-27 at 11:33 +0000, Peter Ruskin wrote:
> On Sunday 27 March 2005 11:11, Nick Rout wrote:
> > On Sun, 2005-03-27 at 09:17 +0000, Julien Cayzac wrote:
> > > On Fri, 25 Mar 2005 19:22:53 +0000, Neil Bothwick 
> <[EMAIL PROTECTED]> wrote:
> > > > Occasionally, but you'll get a warning that you need to do
> > > > this when you sync. I think the last time this happened on
> > > > x86 was when the 1.4 profile was deprecated last year.
> > >
> > > Even after syncing, I still don't get any make.defaults, so eix
> > > is now broken:
> > >
> > > # eix -u
> > > Updating eix database in /var/cache/eix
> > > Using portage cache: /usr/portage/metadata/cache/
> > > varsreader.cc:309 Can't open file
> > > /etc/../usr/portage/profiles/default-linux/x86/2005.0/make.defa
> > >ults No such file or directory
> >
> > what does ls -l /etc/make.profile say?
> >
> > try rm /etc/make.profile
> >
> > ln -s /etc/make.profile
> > /usr/portage/profiles/default-linux/x86/2005.0
> >
> That's bad advice Nick ;-)
> 
> First: ln -s <source> <link> means you probably meant ln 
> -s /usr/portage/profiles/default-linux/x86/2005.0 /etc/make.profile

woops yes I got my parameters round the wrong way there, sorry about
that!

> 
> Second: That won't work for Neil anyway, because there is 
> no /usr/portage/profiles/default-linux/x86/2005.0/make.defaults
> 

err I never suggested that he switch to the 2005.0 profile in the first
place, someone else did. I was just trying to make sure he had his link
right (which, as you pointed out above) I did wrong! 

However on this second point I think you may be wrong. 

/usr/portage/profiles/default-linux/x86/2005.0/parent contains .. and as
I understand it this points to the directory above
(i.e /usr/portage/profiles/default-linux/x86/ which contains a
make.defaults.

Although so does /usr/portage/profiles/default-linux/x86/2004.3/parent,
yet /usr/portage/profiles/default-linux/x86/2004.3/ contains a
make.defaults, so now I am confused!


-- 
Nick Rout <[EMAIL PROTECTED]>

--
[email protected] mailing list

Reply via email to