Re: [Synaptic-devel] [Bug #3311] support /etc/apt/sources.list.d/

[Panu Matilainen]

On Thu, 24 Apr 2003, Michael Vogt wrote:

> On Thu, Apr 24, 2003 at 09:41:22AM +0300, Panu Matilainen wrote:
> > 
> > (Savannah throws a php error at me when trying to create an account so
> > commenting through mail..)
> > 
> > On Wed, 23 Apr 2003 address@hidden wrote:
> > 
> > > ------------------ Additional Follow-up Comments 
> > > ----------------------------
> > 
> > > Does this mean that it does not display it in the sources.list editor or
> > > does it mean that it does not use it when you click update?
> > 
> > Both.
> > 
> > Synaptic doesn't see anything in the sources.list.d directory since it's
> > doing all the reading and parsing of sources.list by itself. I have
> > beginnings of a patch to add support for it, it's easy to make it read the
> > sources.list.d stuff (basically just copy the relevant code from apt-rpm),
> > editing them sanely is another issue: without proper support for it in the 
> > editor the changes will be written to sources.list instead of the 
> > originating sources.list.d entry. I started work on it as well but 
> > didn't quite finish it (C++ is anything but "native tongue"  for me :).
> 
> Great to hear that you are working on this :)
> 
> Please let me know once there is something I can test and help
> debugging. 

Probably a lot :) Dunno when I have more time to look into it however..

> 
> One problem is that debians apt-get IIRC does not support
> sources.list.d style dirs. This isn't optimal as it give the debian
> users different packages if they use synaptic (versus plain
> apt-get). 

Indeed. The sources.list.d thingy is quite new addition to apt-rpm and I
don't know how much Gustavo and Jason exchange stuff like this at all.  
This probably would be worth it, since there already are vendors.list.d
and apt.conf.d as well. Although.. since synaptic does it's own parsing of
those files I don't think it matters that much: if you don't have
Dir::Etc::sourceparts set, it'll just ignore the whole thing so it might
not be even necessary to #ifdef the thingy.

> 
> The next thing that's probably a bit problematic is that the
> sources.list editor itself is not yet made with glade. I have a glade
> model checked into svn but no code is written yet (this is only
> relevant if you want to change this editor to show e.g. what files in
> sources.list.d are edited).

I started doing this so that each source list entry has association to the
file it came from but not showing that in the editor. I got it basically
working except for the actual files got truncated to zero length :-/
Probably some really silly detail I missed, but was too tired to think 
straight at the time - I'll try to look into it again one of these days.

Another thing I considered is disabling the editing of sources.list.d
entries completely, simply show them in the editor as uneditable: I
consider the sources.list.d entries something which packages drop in there
instead of messing with sources.list, if user wants to add something
he/she can edit sources.list directly so I don't think that would be a big
problem.  Or then it's just plain confusing for the user :)

Comments / ideas on how to best implement that are most welcome...

> 
> OTOH, we can make this feature rpm only and no debian user will notice
> (no one will probably notice anyway as they don't have a
> sources.list.d dir :).

Indeed :)

        - Panu -