"Bernhard R. Link" <[EMAIL PROTECTED]> writes:
> * Goswin von Brederlow <[EMAIL PROTECTED]> [060609 11:47]:
>> I'm totaly fine with removing all packages that are no longer in the
>> new Packages file _and_ exporting the index. Sure packages will be
>> missing then until the updates come in but I can live with that. I
>> have my local mirror and ftp.de.debian.org in sources.list anyway so
>> there is a fallback.
>
> Well, clearly documented that this would have this results (packages
> being flagged obsolete by clients not having another source; bloated
> pdiffs generated if those are configured), that might be an acceptable
> new command.
>
> Something useable for other situations might be nice though. Could
> perhaps some command to update only a given architecture help?
> (That way only the arch-indep packages would be all the time doubled
> while at most one architecture has old and new arch-dependent files
> lying around).
>
>> I would implement this as a seperate "reprepro cleanup" command that
>> updates all Packages/Sources files but then only runs the '-' rule in
>> updates. That should be simple to implement and make it clear enough
>> that to users that they are purposefully removing packages without
>> updates in place.
>
> Well, it'd get a bit more complicated, as packages to be upgraded do not
> get removed, but only replaced once the new package is ready. (Otherwise
> an error to download something would result in packages getting removed
> instead of upgraded). But writing a new command to remove when to be
> removed and remove when to be upgraded should not be that complicated
> and I'll look into it next time I edit reprepro's code.
>
> Hochachtungsvoll,
> Bernhard R. Link
Thanks.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
