Mick wrote:
> On Sunday, 28 April 2019 22:49:42 BST Dale wrote:
>> [email protected] wrote:
>>> Thanks to all who reponded:
>>>   - Rich Freeman suggests:
>>>     - having apache serve the local distfiles.
>>>     
>>>       How?  Just make them available in the apache root and give portage
>>>       the URL somewhere?>     
>>>     - use "infra scripts", but I think that's for running an up-to-date
>>>     general-purpose mirror
>>>     
>>>     He explains later that repos.conf defines the single place where the
>>>     repository is defined but that is distinct from where the distfiles
>>>     come from, which is defined by make.conf:GENTOO_MIRRORS
>>>   
>>>   - Dale suggests:
>>>     - a package, http-replicator, which might do Freeman's first
>>>     
>>>       suggestion.
>>>   
>>>   - Neil Bothwick explains  the difference between serving the "portage
>>>   
>>>     mirror, the repository of ebuild and associated files" and the
>>>     distfiles, and suggests using NFS, presumably instead of, or in
>>>     addition to /usr/portage/distfiles.
>>>     
>>>     Okay, I looked for the first time at the files directly under
>>>     /usr/portage.
>>>     Is it a correct assumption that all packages available for
>>>     installation will be represented there? And that's it?  That's
>>>     basically all there is to a gentoo installation? -
>>>     /usr/portage/distfiles
>>>     - the ebuilds directly under /usr/portage
>>>     - /usr/portage/eclass
>>>     - /usr/portage/metadata
>>>     - /usr/portage/profiles
>>>     - /etc/portage
>>>     
>>>     If so, then I'm delighted in the simplicity of it.  Like reading the
>>>     one page definition of tcl. Unfortunately, it doesn't come through so
>>>     well in the documentation, with things like layouts seemingly basic
>>>     to an understanding.
>>>   
>>>   - Peter Humphrey suggests:
>>>     -  http ftp proxy
>>>     
>>>         In what way is that different from rsync which I thought I'd
>>>         already configured?
>> Just to add some more info.  By changing the settings in make.conf, you
>> can move these directories wherever you like.  As a example, I moved
>> mine here:
>>
>>
>> root@fireball / # ls -al /var/cache/portage/
>> total 160
>> drwxr-xr-x   5 root    root      4096 Dec 20  2012 .
>> drwxr-xr-x  13 root    root      4096 Apr 24 03:18 ..
>> drwxrwxr-x   3 portage portage 143360 Apr 26 04:06 distfiles
>> drwxr-xr-x 105 portage portage   4096 Apr 26 04:04 packages
>> drwxr-xr-x 174 portage portage   4096 Apr 22 23:32 tree
>> root@fireball / #
>>
>>
>> I have these settings in make.conf to match where I put things:
>>
>>
>>
>> DISTDIR="/var/cache/portage/distfiles/"
>> PKGDIR="/var/cache/portage/packages"
>> PORTDIR="/var/cache/portage/tree"
> Just to mention the PORTDIR variable is no longer meant to be declared in /
> etc/portage/make.conf, but in /etc/portage/repos.conf/gentoo.conf, using the 
> 'location = ' directive.  See URL below:
>
> https://wiki.gentoo.org/wiki/PORTDIR
>
>


I wasn't aware of the move or don't remember it if I read it somewhere. 
Thanks for noticing that since that could cause confusion.  I bet if I
ever move that again, I'll forget that it is in a new place.  :/

Dale

:-)  :-) 

Reply via email to