Re: Large data packages in the archive
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Luk Claes wrote:
>
> Are you sure that the current sync scripts make that possible and won't
> sync everything unless explicitely stated differently and will keep
> working without intervention for the time being? Because otherwise it's
> like Joerg said not an option IMHO.
I can't tell for sure, but I don't even think that's relevant.
Because let's say source package foo is already in the archive and builds
foo and foo-data, the former being an arch-dependent package and the latter
independent. If the 'data' component is added, next upload of foo should
build foo-data placing it under 'data', causing no more traffic than the
one caused by a new upload of foo without the data component.
Then, if the addition of the new component is scheduled just after lenny is
released (just an example), it would give some time to mirror admins to
take a decision, and even more time before lenny+1 is released to stop
mirroring the data component (considering it is automagically mirrored).
My POV is that way 'b' causes less pain and less work than option 'c' and
achieves the same goal without having to setup another repository which
would also require more integration work in the current tools (package.d.o,
PTS, DDPO, DEHS, <insert your favourite tool here>).
And if that change is defined as a lenny+1 RC goal, it would ensure that all
data packages are in the data component for lenny+1 (which I don't think
are too many).
Please correct me if my assumption is wrong.
>
> Cheers
>
> Luk
Cheers,
Raphael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIOdiVYy49rUbZzloRApp9AJ9QK9igtCxUXIjl3o3YDKw9wtLhvwCeJyna
QuJfLQ7G1BvQKdNBbyXVJCI=
=/zsL
-----END PGP SIGNATURE-----
Reply to: