Re: Bug#467650: debian-edu: Downloads things, does not clean up after itself.
On Tue, Feb 26, 2008 at 10:46:59PM +0100, Andreas Tille wrote:
> On Tue, 26 Feb 2008, Petter Reinholdtsen wrote:
>
>>> There are a few problems with this:
>>> - It's missing a build dependency on apt, which isn't part of
>>> essential + build essential.
>>
>> Good point. Need to be fixed.
>
> Yes it should. IMHO the simplest solution would be to make
> cdd-dev dependant from apt.
> On the other hand - why isn't apt not part of essential?
Because it's not. What is part of essential is dpkg.
>>> - Since you download things, the sources aren't available for it,
>>> so I don't see how you comply with the DFSG. (Or I have no
>>> idea why you download things.)
>>
>> The package check if there is net, and if there is net it download the
>> list of packages available from the debian repository of choice and
>> uses this information to filter the priority of the list of wanted
>> packages to generate tasksel tasks and meta packages (packages with
>> only dependencies). As the list of available packages differ over
>> time, as well as differ from architecture to architecture, the
>> generated package lists are supposed to reflect this. It is the
>> purpose of this package.
>
> I fail to see the actual conflict with DSFG. Kurt, could you please
> specify the point you have in mind that conflicts? I hope this is
> not the point why you tagged the bug grave because I do not see a good
> chance to change this.
>From that description I have to wonder why you need to download all
those .deb files. Can't you do the same thing with just the Packages
file?
Since it doesn't actually seem to be doing much with the .deb's it
downloads, I don't see a problem anymore.
>>> - Since it's not put in the build dir, it doesn't get cleaned up.
>>
>> This should be fixed too.
>
> Well, if we would fix it we will have to refuse the option to profit from
> this "cache" if you work offline. This is no big loss, but putting it
> outside the build dir was intended for exactly the purpose to have it
> not cleaned up. I admit that it is not really a clean solution. We
> might think about reading an environment variable, say OFFLINE=yes
> and keep the cache if this is set, while removeing it otherwise. This
> should be done in cdd-dev package.
Putting it in some arbitrary path isn't very useful. If all packages
start to write to "../tmp" and store something there, sooner or later
things will break.
Kurt
Reply to: