Darren Salt <[EMAIL PROTECTED]> writes:
> I demand that Goswin von Brederlow may or may not have written...
>
>> Darren Salt <[EMAIL PROTECTED]> writes:
>>> I demand that Matthias Julius may or may not have written...
>>> [snip]
>>>> I think a more elegant solution would be if aptitude had a command to
>>>> install build-depends.
>>> <AOL>.
>>>> It could attach a new flag to a package that causes aptitude to treat
>>>> build-depends just like depends of that package. [...]
>
>>> Maybe... just installing the build-depends with any necessary marking as
>>> automatically installed would be good enough - possibly regardless of
>>> whether they're explicitly mentioned as build-dependencies?
>
>> Then they get removed the next time you run aptitude and not when you stop
>> using the source.
>
> Well, yes. Perhaps I should have explicitly qualified that - "but only if
> they're depended upon by other build dependencies" - but "any necessary
> marking" seemed to cover it. Marking them all would indeed be daft.
Packages that something depends on don't get removed anyway. Automatic
or not. The only intresting bits are those without anything depending
on them.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
