Bug#160743: Cleanup

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#160743: Cleanup

Michael Vogt via nm-2
Hi,

I agree with the idea that after a successful install/upgrade we want to
remove the downloaded
debs. There are setups (like pbuilder) that want to keep the cache files
but those seem to be
not the common case. Attached is a quick patch to implement the removal.
We can tweak
the name and the default for "Apt::Keep-Downloaded-Debs" of course :)
Test-case is missing
but will soon follow if there is agreement on this.

Cheers,
 Michael

cleanup.diff (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bug#160743: Cleanup

Simon Richter-2
Hi,

On 02.01.2016 12:30, Michael Vogt wrote:

> I agree with the idea that after a successful install/upgrade we want to
> remove the downloaded
> debs.

Would it make sense to use "autoclean" for this? It seems to implement
precisely what we want -- clean packages that can no longer be
downloaded from any source, and, depending on the "APT::Clean-Installed"
option, also those installed on the local system.

   Simon


signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bug#160743: Cleanup

Julian Andres Klode-4
On Sat, Jan 02, 2016 at 06:57:25PM +0100, Simon Richter wrote:

> Hi,
>
> On 02.01.2016 12:30, Michael Vogt wrote:
>
> > I agree with the idea that after a successful install/upgrade we want to
> > remove the downloaded
> > debs.
>
> Would it make sense to use "autoclean" for this? It seems to implement
> precisely what we want -- clean packages that can no longer be
> downloaded from any source, and, depending on the "APT::Clean-Installed"
> option, also those installed on the local system.
>

I don't know what APT::Clean-Installed does, but last time I looked,
it was non-sense, and not the behavior we want.

Furthermore, we want that to run automatically; and I would exclude
packages from it that are no longer available. That is, to be
automatically removed from the cache, the package must be:

(1) installed in the current run
(2) available in a non-volatile source (which basically follows
    from 1)

It's entirely different to what autoclean does, as that removes
packages which are no longer available.

--
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.