On Mon, Apr 09, 2001, Chris Gray wrote: > On Mon, 09 Apr 2001, Colin Watson wrote: > > Mario Vukelic <[EMAIL PROTECTED]> wrote: > >>My locally generated debs, e.g. from kernel compiles, show up as > >>obsolete in dselect. Is there an easy way to tell their locations to > >>the package manager or do I have to mess with Packages.gz files and > >>the like? > > > > You pretty much have to mess with Packages.gz, I'm afraid (at least, > > that's the easiest way I can think of). apt-ftparchive in the > > apt-utils package in testing/unstable may help. > > If I understand the question correctly, it seems the canonical answer > is to raise the version number of the locally created package. This > should keep dselect or apt from thinking that the local package is > obsolete. You can change the version of the package by adding to the > debian/changelog file. There is a nice mode in emacs to help you do this.
Hi, At the risk of talking about something I don't really understand fully myself, I believe there's some functionality called 'epochs' built into dpkg, and denoted by 'make-kpkg --revision=2:myrevision' (note the '<n>:' syntax), which has some benefits in this area. I looked into it last time I used kernel-package, but I remember conflicting messages/descriptions from different sources, so I don't recall the full system or the true benefits of epochs. Just wanted to mention it to possibly point you in the right direction. Hope this helps and take care, Daniel > > Cheers, > Chris > > -- > Got jag? http://www.tribsoft.com -- Daniel A. Freedman Laboratory for Atomic and Solid State Physics Department of Physics Cornell University
