On Tue, Mar 02, 2010 at 11:56:58AM -0500, 7v5w7go9ub0o wrote:
> On 03/01/10 18:09, Neil Bothwick wrote:
> > On Mon, 01 Mar 2010 14:07:07 -0500, 7v5w7go9ub0o wrote:
> >
> >>> Or you can edit /var/lib/layman/make.conf and change the
> >>> locations there.
> >>
> >> That didn't work for me; the curren
On Mon, 01 Mar 2010 14:07:07 -0500, 7v5w7go9ub0o wrote:
> > Or you can edit /var/lib/layman/make.conf and change the locations
> > there.
>
> That didn't work for me; the current layman script still references the
> old location; which is why I added the soft link.
You have to set the locatio
On Monday 01 March 2010 22:19:45 Tanstaafl wrote:
> On 2010-03-01 1:26 PM, Nikos Chantziaras wrote:
> > Or you can edit /var/lib/layman/make.conf
>
> Also - why /var/lib/layman, and not /var/lib/portage/layman? It looks a
> little odd just dumped in there all by itself.
Becuase layman is not par
On 2010-03-01 1:26 PM, Nikos Chantziaras wrote:
> Or you can edit /var/lib/layman/make.conf
Also - why /var/lib/layman, and not /var/lib/portage/layman? It looks a
little odd just dumped in there all by itself.
--
Charles
On 2010-03-01 2:02 PM, 7v5w7go9ub0o wrote:
> I did; I simply moved the whole layman directory. Works.
Yeah, but I didn't start off using layman when I added my first local
ebuild a long time ago, so they are not under layman - they are at the
same level - ie, /usr/local/portage contains:
/app-adm
5 matches
Mail list logo
