Legacy mirror structure

Jesse Keating jkeating at j2solutions.net
Tue Jan 20 16:29:41 UTC 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 20 January 2004 04:46, Warren Togami wrote:
> I totally agree here.  "apt-get" source would also potentially fail on
> many of the RH packages due to the prevalent missing BuildRequires.
> Legacy's target users are NOT developers who use the SRPMS often.
>
> For this reason I would not include SRPMS for the base distribution nor
> the almost as numerous RH supplied updates.  I would include only SRPMS
> of Legacy supplied updates, as Legacy QA and buildsystem necessitates
> fixing BuildRequires, so "apt-get source" at least has a chance of
> working properly (but it still is not very useful at all).
>
> You make mirroring faster by leaving out those THOUSANDS of SRPMS that
> 0.001% of the users would use.  You make client usage faster by leaving
> it out.  You make it far less of a burden in mirror administration by
> making Legacy as small as possible by default.

I'm convienced to put the SRPMS in a different area for repot purposes, but 
I will not remove it from the server.  I've had too many headaches with 
that.

> Jesse was earlier grappling with the problem of the ugly symlink for a
> unified SRPMS for all archs.  Using a structure like this would work
> wonderfully, while very conveniently placing all archs and the SRPMS at
> the same level.

No longer grappling, if I put SRPMS in their own repository.  No longer 
need symlinks.

> Something like:
> $distnumber/$repository/$basearch/*.rpm
>
> Example:
> 7.2/updates/SRPMS/repodata/ <--- XML metadata
> 7.2/updates/SRPMS/headers/  <--- yum native headers
> 7.2/updates/i386/repodata/  <--- XML metadata
> 7.2/updates/i386/headers/   <--- yum native headers
> 7.2/updates/base/           <--- non-flat apt genbasedir location (*)
> 7.2/legacy/SRPMS/repodata/
> 7.2/legacy/SRPMS/headers/
> 7.2/legacy/i386/repodata/
> 7.2/legacy/i386/headers/
> 7.2/legacy/base/
>   . . .
> 1/updates/SRPMS/repodata/
> 1/updates/SRPMS/headers/
> 1/updates/i386/repodata/
> 1/updates/i386/headers/
> 1/updates/x86_64/repodata/
> 1/updates/x86_64/headers/
> 1/updates/base/

UGH!  I don't like splitting inside the /updates dir the extra archs.  I'd 
rather split it at a higher level.

- -- 
Jesse Keating RHCE MCSE	(http://geek.j2solutions.net)
Fedora Legacy Team	(http://www.fedora.us/wiki/FedoraLegacy)
Mondo DevTeam		(www.mondorescue.org)
GPG Public Key		(http://geek.j2solutions.net/jkeating.j2solutions.pub)

Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=jkeating
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFADVd14v2HLvE71NURAp12AJ0cLFAQ0u/xuQi0BOGRJEzYJyaWigCfY7lh
ISLBIpi9HIRFYFMBGNbVFwc=
=tVgl
-----END PGP SIGNATURE-----





More information about the fedora-legacy-list mailing list