1 |
Apparently, though unproven, at 18:36 on Sunday 28 November 2010, Mick did |
2 |
opine thusly: |
3 |
|
4 |
> On Sunday 28 November 2010 15:28:01 Alan McKinnon wrote: |
5 |
> > Apparently, though unproven, at 11:07 on Sunday 28 November 2010, Mick |
6 |
> > did |
7 |
> > |
8 |
> > opine thusly: |
9 |
> > > > This doesn't look right. layman has never installed overlays in that |
10 |
> > > > location for me. |
11 |
> > > |
12 |
> > > Hmm ... it does for me! o_O |
13 |
> > > |
14 |
> > > $ ls -la /var/lib/layman/enlightenment/ |
15 |
> > > total 16 |
16 |
> > > drwxr-xr-x 25 root root 25 Nov 27 10:33 . |
17 |
> > > drwxr-xr-x 3 root root 8 Nov 27 10:33 .. |
18 |
> > > drwxr-xr-x 4 root root 4 Nov 27 10:33 app-admin |
19 |
> > > drwxr-xr-x 4 root root 4 Nov 27 10:33 app-misc |
20 |
> > |
21 |
> > Well now, that's just fscking brain dead. Putting data files into areas |
22 |
> > of the file system where executables were there first. Tut, tut, tsk, |
23 |
> > tsk. |
24 |
> > |
25 |
> > Now that I think about it, I recall layman doing something like this the |
26 |
> > first time I used it. It drives me batty, along with portage putting the |
27 |
> > tree in /usr/portage so now layman.cfg has this on all my machines |
28 |
> > |
29 |
> > storage : /var/portage/local/layman |
30 |
> > |
31 |
> > and I *always* change $PORTDIR to be /var/portage |
32 |
> > |
33 |
> > |
34 |
> > I'd forgotten *why* I always do this. Thanks for the reminder. |
35 |
> |
36 |
> The plot thickens ... |
37 |
> |
38 |
> I seem to have set up: |
39 |
> |
40 |
> PORTAGE_TMPDIR=/var/tmp |
41 |
> PORTDIR=/usr/portage |
42 |
> DISTDIR=/usr/portage/distfiles |
43 |
> PKGDIR=/usr/portage/packages |
44 |
> PORT_LOGDIR=/var/log/portage |
45 |
> PORTDIR_OVERLAY=/usr/local/portage |
46 |
> |
47 |
> and fair enough layman is in there: |
48 |
> |
49 |
> $ ls -la /usr/local/portage/ |
50 |
> total 2 |
51 |
> drwxr-xr-x 3 root root 3 Jun 10 16:38 . |
52 |
> drwxr-xr-x 10 root root 13 Jun 8 22:16 .. |
53 |
> drwxr-xr-x 2 root root 3 Jun 10 16:38 layman |
54 |
> |
55 |
> but it's empty, except for a make.conf file: |
56 |
> |
57 |
> $ cat /usr/local/portage/layman/make.conf |
58 |
> PORTDIR_OVERLAY="" |
59 |
> |
60 |
> I am guessing that updating/reinstalling layman shifted storage around to |
61 |
> its default: |
62 |
> |
63 |
> storage : /var/lib/layman |
64 |
> |
65 |
> and the make.conf file in there says: |
66 |
> |
67 |
> $ cat /var/lib/layman/make.conf |
68 |
> PORTDIR_OVERLAY=" |
69 |
> /var/lib/layman/enlightenment |
70 |
> $PORTDIR_OVERLAY |
71 |
> " |
72 |
> |
73 |
> I recall that after some version the default layman overlays location |
74 |
> changed and there was a post in this list too (but forget when). |
75 |
> |
76 |
> Perhaps if you post a bug for a more sane storage location, then the layman |
77 |
> devs will make a more considered decision on this. |
78 |
|
79 |
I'm starting to remember more about this now. There was an elog about these |
80 |
changed directories a while back, I read them and realized I didn't have to do |
81 |
anything as my layman configs now had explicit directories and didn't rely on |
82 |
defaults anymore. |
83 |
|
84 |
I don't think a feature request will go anywhere. The layman dev recently |
85 |
changed things, and the fight about PORTDIR has been going on since there was |
86 |
a portage. All whinging about the location of PORTDIR thus far has led to |
87 |
exactly nothing. Occasionally one sees feedback on b.g.o. about how the |
88 |
default is just a default, feel free to change it. |
89 |
|
90 |
On more business matters, have the ebuilds in enlightenment overlay |
91 |
successfully installed for you? And has the category for EFL's media libs |
92 |
settled down? This business of media-libs vs x11-libs caused me huge amounts |
93 |
of grief about a year ago.... |
94 |
|
95 |
|
96 |
-- |
97 |
alan dot mckinnon at gmail dot com |