1 |
n952162@×××.de wrote: |
2 |
> Thanks to all who reponded: |
3 |
> |
4 |
> - Rich Freeman suggests: |
5 |
> - having apache serve the local distfiles. |
6 |
> How? Just make them available in the apache root and give portage the URL somewhere? |
7 |
> - use "infra scripts", but I think that's for running an up-to-date general-purpose mirror |
8 |
> |
9 |
> He explains later that repos.conf defines the single place where the |
10 |
> repository is defined but that is distinct from where the distfiles |
11 |
> come from, which is defined by make.conf:GENTOO_MIRRORS |
12 |
> |
13 |
> - Dale suggests: |
14 |
> - a package, http-replicator, which might do Freeman's first |
15 |
> suggestion. |
16 |
> |
17 |
> - Neil Bothwick explains the difference between serving the "portage |
18 |
> mirror, the repository of ebuild and associated files" and the |
19 |
> distfiles, and suggests using NFS, presumably instead of, or in |
20 |
> addition to /usr/portage/distfiles. |
21 |
> |
22 |
> Okay, I looked for the first time at the files directly under /usr/portage. |
23 |
> Is it a correct assumption that all packages available for installation will be represented there? |
24 |
> And that's it? That's basically all there is to a gentoo installation? |
25 |
> - /usr/portage/distfiles |
26 |
> - the ebuilds directly under /usr/portage |
27 |
> - /usr/portage/eclass |
28 |
> - /usr/portage/metadata |
29 |
> - /usr/portage/profiles |
30 |
> - /etc/portage |
31 |
> |
32 |
> If so, then I'm delighted in the simplicity of it. Like reading the one page definition of tcl. |
33 |
> Unfortunately, it doesn't come through so well in the documentation, |
34 |
> with things like layouts seemingly basic to an understanding. |
35 |
> |
36 |
> - Peter Humphrey suggests: |
37 |
> - http ftp proxy |
38 |
> |
39 |
> In what way is that different from rsync which I thought I'd already configured? |
40 |
> |
41 |
> |
42 |
|
43 |
Just to add some more info. By changing the settings in make.conf, you |
44 |
can move these directories wherever you like. As a example, I moved |
45 |
mine here: |
46 |
|
47 |
|
48 |
root@fireball / # ls -al /var/cache/portage/ |
49 |
total 160 |
50 |
drwxr-xr-x 5 root root 4096 Dec 20 2012 . |
51 |
drwxr-xr-x 13 root root 4096 Apr 24 03:18 .. |
52 |
drwxrwxr-x 3 portage portage 143360 Apr 26 04:06 distfiles |
53 |
drwxr-xr-x 105 portage portage 4096 Apr 26 04:04 packages |
54 |
drwxr-xr-x 174 portage portage 4096 Apr 22 23:32 tree |
55 |
root@fireball / # |
56 |
|
57 |
|
58 |
I have these settings in make.conf to match where I put things: |
59 |
|
60 |
|
61 |
|
62 |
DISTDIR="/var/cache/portage/distfiles/" |
63 |
PKGDIR="/var/cache/portage/packages" |
64 |
PORTDIR="/var/cache/portage/tree" |
65 |
|
66 |
|
67 |
If you need to move things to a place that is more convenient for you, |
68 |
it is doable. The only thing I don't think you can move is /etc/portage |
69 |
itself. I think that has to be there. Other than that, move things |
70 |
where you need them to be. There are others who have placed theirs in |
71 |
other places and as long as you tell portage where it is at, you can |
72 |
adjust them as needed. |
73 |
|
74 |
Hope that extra info helps. |
75 |
|
76 |
Dale |
77 |
|
78 |
:-) :-) |