2009/2/4 Celso Providelo <email address hidden>:
> Martin,
>
> Thanks for you comments, right the implementation is beneficial in a
> sense that superseded/old packages could still be handled via Synaptic.
>
> The drawback is that packages that remain published in the repository
> cost us 2x disk space (librarian + repository disk). We are almost fine
> with keep old sources in librarian for a long time, but not that happy
> about duplicating the space consumption for keeping them in the
> repository as well.
>
> Do you see my point ?
I do. I hadn't realized that the repository disk was separate from
the librarian disk. I though the repository pointed (by http
redirects or rewrites) into the librarian.
I still think keeping old versions for some period of time would be
highly useful, and it could be capped so as not to use too much space.
2009/2/4 Celso Providelo <email address hidden>:
> Martin,
>
> Thanks for you comments, right the implementation is beneficial in a
> sense that superseded/old packages could still be handled via Synaptic.
>
> The drawback is that packages that remain published in the repository
> cost us 2x disk space (librarian + repository disk). We are almost fine
> with keep old sources in librarian for a long time, but not that happy
> about duplicating the space consumption for keeping them in the
> repository as well.
>
> Do you see my point ?
I do. I hadn't realized that the repository disk was separate from
the librarian disk. I though the repository pointed (by http
redirects or rewrites) into the librarian.
I still think keeping old versions for some period of time would be
highly useful, and it could be capped so as not to use too much space.
-- launchpad. net/~mbp/>
Martin <http://