On Sat, Jun 17, 2006 at 02:49:50PM -0700, Leonard Chatagnier wrote:
--- Wackojacko <[EMAIL PROTECTED]> wrote:
> Leonard Chatagnier wrote:
snip........
Looks like you still want a mechanism for keeping specific versions of
specific packages in cache.
What I do is copy the .debs elsewhere, such as /usr/local/debs/
That way they stay around, at the cost of some duplicaiton.
Hmmm. Maybe a hard-link from /usr/local/debs/ to the .deb in tha cache?
That way when the cache file is deleted, the hard-link will still keep
that file intact. But then you might want to use something likd
/var/local/debs/ so that keep-directory resides on the same file-system
as the target of the hard-links. Soft-links (which cross file-systems)
won't work for this.
-- hendrik
Yes, I do but more importantly, an explanation of why I have a 2.4.27 and
2.6.8 kernel images in the cache(they are not sid) along with the 2.6.16 KI.
Would not auto-clean remove the 2.4.27 and 2.6.8 images also. Something is
inconsistent here, to me anyway, and an explanation would enlighten me. Aptitude
auto removed the 2.6.15-1-686 KI and left 2.6.8 and 2.6.16 KI's installed
otherwise
all this wouldn't have ever come up.
Thanks for any feedback.
Leonard Chatagnier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
