On Wed, Jun 24, 2015 at 11:25:54PM +0200, Johannes Schauer wrote:
Hi,
Quoting David Kalnischkies (2015-06-24 23:18:12)
So, long story short, the solution I would like to propose is:
$ apt-get files Codename: sid Trusted: yes Created-By: Packages
[…]
so the arguments to apt-get
On Thu, Jun 26, 2014 at 10:58:38PM +0200, David Kalnischkies wrote:
On Thu, Jun 26, 2014 at 10:30:24PM +0200, Johannes Schauer wrote:
Quoting David Kalnischkies (2014-06-26 21:48:42)
I think it is a bad idea to use our lib-directory directly.
if apt developers agree that it is a bad
Hi,
Quoting David Kalnischkies (2015-06-24 23:18:12)
So, long story short, the solution I would like to propose is:
$ apt-get files Codename: sid Trusted: yes Created-By: Packages
[…]
so the arguments to apt-get files are fields and values and the command will
output all paragraphs where
On Thu, Jun 26, 2014 at 11:13:28PM +0200, Johannes Schauer wrote:
Hi,
Hi,
[..]
I was thinking that it would nice if apt would provide an API to retrieve the
location and properties of Packages and Sources files in /var/lib/apt/lists
If apt had such an interface, then third party
On Thu, Jun 26, 2014 at 11:13:28PM +0200, Johannes Schauer wrote:
Quoting David Kalnischkies (2014-06-26 22:58:38)
If apt had such an interface, then third party applications which make use of
Packages and Sources files like dose3, ben and botch could directly make use
of
those files and the
Hi,
Quoting David Kalnischkies (2014-07-08 19:24:33)
Well, I still kinda like my workaround presented in my first mail as
it tries to solve this usecase at a higher level, which you haven't
commented on so far.
Sorry, let me do that now:
If you like REALLY want to go the extra mile, you
On Wed, Jun 25, 2014 at 10:16:57PM +0200, Johannes Schauer wrote:
some software in Debian works on Packages and Sources files. Instead of
retrieving those from mirrors they could re-use the copies which are
likely present in /var/lib/apt/lists/. But there exists no way to ask
apt which mirror,
Hi David,
Quoting David Kalnischkies (2014-06-26 21:48:42)
I think it is a bad idea to use our lib-directory directly.
if apt developers agree that it is a bad idea to allow 3rd party software
access /var/lib/apt/lists, then please close this bug report.
I will then redirect those who want
On Thu, Jun 26, 2014 at 10:30:24PM +0200, Johannes Schauer wrote:
Quoting David Kalnischkies (2014-06-26 21:48:42)
I think it is a bad idea to use our lib-directory directly.
if apt developers agree that it is a bad idea to allow 3rd party software
access /var/lib/apt/lists, then please
Hi,
Quoting David Kalnischkies (2014-06-26 22:58:38)
For binary packages this exists already, but not for sources packages. There
is (also) no (simple) mapping from sources.list to Packages/Sources files and
back. Both could surely be added if we have a compelling reason/user for
this. apt-*
Package: apt
Version: 1.0.1
Severity: wishlist
Hi,
some software in Debian works on Packages and Sources files. Instead of
retrieving those from mirrors they could re-use the copies which are
likely present in /var/lib/apt/lists/. But there exists no way to ask
apt which mirror, suite or
On Wed, Jun 25, 2014 at 10:16 PM, Johannes Schauer j.scha...@email.de wrote:
Package: apt
Version: 1.0.1
Severity: wishlist
Hi,
some software in Debian works on Packages and Sources files. Instead of
retrieving those from mirrors they could re-use the copies which are
likely present in
Hi Julian,
Quoting Julian Andres Klode (2014-06-25 22:28:51)
That software should use the API provided by APT to access APT files. The
layout of /var/lib/apt/lists and the contents of the files is an
implementation detail, we already broke the expectations of others once when
we renamed
On Wed, Jun 25, 2014 at 10:34 PM, Johannes Schauer j.scha...@email.de wrote:
Hi Julian,
Quoting Julian Andres Klode (2014-06-25 22:28:51)
That software should use the API provided by APT to access APT files. The
layout of /var/lib/apt/lists and the contents of the files is an
implementation
Hi,
Quoting Julian Andres Klode (2014-06-25 22:40:40)
Now I understand what you mean. I thought you meant the location of the files
on disk. Do you mean the location on the mirror instead? Stuff like
architecture, etc. is exported in the cache in pkgCache::PackageFile.
All of it. The
On Wed, Jun 25, 2014 at 10:56 PM, Johannes Schauer j.scha...@email.de wrote:
Hi,
Quoting Julian Andres Klode (2014-06-25 22:40:40)
Now I understand what you mean. I thought you meant the location of the files
on disk. Do you mean the location on the mirror instead? Stuff like
architecture,
Hi,
Quoting Julian Andres Klode (2014-06-25 23:02:33)
Well, as I said WRT on disk. We expose this, but you should most likely not
use it without APT parsers, as it may not contain data you expect (for
example, compressed indices). Using APT's parsers for those files is the best
idea.
what
On Wed, Jun 25, 2014 at 11:30 PM, Johannes Schauer j.scha...@email.de wrote:
Hi,
Quoting Julian Andres Klode (2014-06-25 23:02:33)
Well, as I said WRT on disk. We expose this, but you should most likely not
use it without APT parsers, as it may not contain data you expect (for
example,
Hi,
Quoting Julian Andres Klode (2014-06-26 00:20:44)
You can enable storing them in compressed form without uncompressing them
first. APT transparently handles compressed files. We do not need to store
that information anywhere, because of that. As said, the files in there are
an
19 matches
Mail list logo
