Re: Mirror layout proposal

On 8/1/03 3:54 PM, "Mark Guertin" <[email protected]> wrote:

>> * Organized distfiles section
>>   It's my opinion that the distfiles should be kept in subcategories.
>> In my opinion there should be a folder per application, ie all
>> app-admin/foo distfiles be placed in an app-admin/foo/ subcategory. Of
>> course, this would require that some ebuilds that use the same distfiles
>> be tweaked to download such shared files into the most logical 'parent'
>> directory, but we're going to be thrashing the trees rather thoroughly
>> anyway, so that shouldn't be too much of a problem (also, it's not a
>> huge deal to mirror some files multiple times accidentally, and such can
>> be easily remedied later).
> 
> This is not something that is properly do-able at this time afaik.  It would
> mean a rewrite of large portions of porteus because it always defaults to a
> single mirror location (i.e. Mirror:/distfiles/ ) and cannot be set within
> builds to do it differently aside from removing that functionality from
> porteus and updating ever ebuild by hand to point to the mirror locations
> first).
> 
> As messy as it is I think we are more stuck with a single (huge) folder
> holding the sources until we can build in a better mechanism.
> 
> Also we should avoid duplication of files on mirrors, that is just _asking_
> for trouble.  I.E. One tarball gets updated, the other doesn't and chaos
> will happen.  Vendors update tarballs without doing revision bumps all too
> often which can lead to complications for all.


Also just had another thought on this.  This would prevent us from having
multiple categories with the same packages without having funky symlinks or
duplicated code.  This may be very desirable if not mandatory on some
arches.

Mark