Steve Greenland wrote:
>
> Aptitude shows a group of "obsolete and locally created packages".
> However, it doesn't distinguish between them, as far as I can tell,
> which is what Marc (and I) would like.
There really is no current way to do this. Case in point: if you use
wget and dpkg -i to install a package, it will still be in the Debian
Packages and thusly be tracked by the front ends.
If you create it locally, or via a -src or -installer, then it is the
same as the above but gets obsoleted. ie: installed by hand, no record
of the package in Packages.
The solution to this that I see is a database similar to Packages, that
lists the package names along with 1) the last released version, 2)
all versions released, or 3) (my preferred) all versions released in the
last release made (ie: all versions in Sarge)
This way the front-ends can compare the installed version to the one(s)
listed in Obsoletes, and if there is a match, warn the user.
This allows the front-ends to ignore locally installed packages, and
those Obsolete packages that have been locally re-built.
It also forces yet another file that has to be downloaded by the back
ends, and parsed by the front ends.
I am willing to work on formats and debugging. I don't really want to
mess with apt* internals.
--
John H. Robinson, IV [EMAIL PROTECTED]
http ((((
WARNING: I cannot be held responsible for the above, sbih.org ( )(:[
as apparently my cats have learned how to type. spiders.html ((((
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
