1 |
Am Don, 2002-02-07 um 22.40 schrieb George Shapovalov: |
2 |
> I would feel uneasy having package database sitting in /var (people quite |
3 |
> often allocate separate partition for that one to get some protection for the |
4 |
> rest of the system as this is the one, which changes most often). |
5 |
> Well, in fact I am about /var/db/pkg. To me it was unnatural place to look |
6 |
> for the database of installed packages. I there would be a discussion I would |
7 |
> vote for keeping both portage and db/pkg trees under /usr. |
8 |
> |
9 |
> George |
10 |
> |
11 |
|
12 |
I would like something like: |
13 |
|
14 |
/usr/portage/* -> /usr/share/portage/available |
15 |
/var/db/pkg/* -> /usr/share/portage/installed |
16 |
/usr/portage/profiles -> /usr/share/portage/profiles |
17 |
/usr/portage/distfiles -> /usr/share/portage/archives |
18 |
|
19 |
And the flat hierarchy (as one mails before) of packages in both |
20 |
directories: available and installed! |
21 |
|
22 |
Greetings |
23 |
|
24 |
Sebastian |
25 |
|
26 |
|
27 |
|
28 |
> |
29 |
> On Thursday 07 February 2002 08:32, you wrote: |
30 |
> > I assume the reason that portage is in /usr and db/pkg is in |
31 |
> > /var is that that is where FreeBSD puts ports and db/pkg. |
32 |
> > Of course FreeBSD doesn't have any reason to worry about |
33 |
> > FHS compliance. Since I am compulsive about having up to |
34 |
> > date versions of everything I mount /usr rw, so this is not |
35 |
> > an issue for me personally. |
36 |
> > |
37 |
> > > Chris Moore wrote: [Sat Feb 2 2002, 3:42:32AM EST] |
38 |
> > > |
39 |
> > > > Move the portage package ebuild filetree from /usr/portage to |
40 |
> > > > /var/lib/portage ( See 5.8.3 +-<pkgtool> and cross reference the |
41 |
> > > > purposes of the /usr hierarchy with the purpose of /var which is |
42 |
> > > > summarized as follows: /usr's purpose is shareable read-only data |
43 |
> > > > (ebuilds are updated!) /var's purpose is sharable/unsharable DYNAMIC |
44 |
> > > > application data (such as the ebuild dirtree) and /var/lib has the |
45 |
> > > > specific option for the package tool's dynamic data) |
46 |
> > > |
47 |
> > > I'm not sure that the ebuild dirtree should be considered 'dynamic'. |
48 |
> > > The only time it *needs* to be updated (written) is shortly before doing |
49 |
> > > a merge. Since the merge is going to be going around writing stuff in |
50 |
> > > the /usr tree anyway, updating /usr/portage doesn't seem that bad. I |
51 |
> > > haven't settled on a personal opinion yet, so I'm mostly playing devil's |
52 |
> > > advocate here. |
53 |
> > > |
54 |
> > > Consider a normal case where /usr is actually mounted r/o, such as on a |
55 |
> > > local network of machines where most of the machines mount /usr |
56 |
> > > read-only from a remote file server. In this case, none of these |
57 |
> > > subordinate machines would need to update /usr/portage. If you wanted |
58 |
> > > to install new software, you would do so on the file server where |
59 |
> > > /usr/bin, /usr/lib, /usr/portage, etc. are all mounted r/w, and |
60 |
> > > therefore you could do the 'emerge rsync' as well package merges. |
61 |
> > > |
62 |
> > > Now that I think about it, this same argument would apply to |
63 |
> > > /var/db/pkg, though, so I guess to be consistant the two (/usr/portage |
64 |
> > > and /var/db/pkg) should be in the same place. Do they both belong in |
65 |
> > > /usr? |
66 |
> > > |
67 |
> > > --Chouser |
68 |
> > > _______________________________________________ |
69 |
> > > gentoo-dev mailing list |
70 |
> > > gentoo-dev@g.o |
71 |
> > > http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
72 |
> _______________________________________________ |
73 |
> gentoo-dev mailing list |
74 |
> gentoo-dev@g.o |
75 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
76 |
-- |
77 |
Sebastian Werner |
78 |
- |
79 |
http://www.werner-productions.de |
80 |
sebastian@××××××××××××××××××.de |
81 |
- |
82 |
Bismarckstraße 51 |
83 |
32427 Minden |
84 |
- |
85 |
Mobile: 0179.4590730 |
86 |
|
87 |
|
88 |
-------------------------------------------------------------------------------- |
89 |
QOTD: |
90 |
"It's hard to tell whether he has an ace up his sleeve or if |
91 |
the ace is missing from his deck altogether." |