Re: This list, and CVS, and stuff
On Thu, 16 Apr 1998, Ian Jackson wrote:
> 2. Controlling dpkg through a pipe: Yes, this should be done. I don't
> think anyone but I can safely make the required modifications, because
> dpkg's internal data structures have different meanings for removal,
> unpack or configure.
I hope you have some time to work on that before 2.1 comes out.
> 3. CVS: is there any documentation on what the Debian setup for this
> is ? Who has read access ? Who has write access ?
I posted a quick summary some time ago to this list, I will dig it up and
send it again.
Read access is anonymous, so everyone can access it. Right now the only
writers in the passwd file are mdorman, guy and juan - mdorman owns the
passwd file (va.debian.org:/cvs/dpkg/CVSROOT/passwd) so he can change
things around. You can always ask me (debian-admin@debian.org) and I'll
do it.
Unless someone is actually using the server right now it would probably be
wise to reset it once the next dpkg release is out and then make use of
it for all subsequent releases.
> 4. Dependency semantics: It's clear to me that not everyone here
> understands fully the intended semantics of dependencies. I posted
> about this some long time ago to debian-devel (I think). I may be
> able to dig this out.
Please do, I have been unable to find some of the precise details I have
occasionally needed - it would be nice to relate my deductions from dpkg's
behavior to your intended design. If you can't find it then can you please
try to re-create it? Right now this issue is pretty high on my list of
things to verify in APT.
Thanks,
Jason
--
To UNSUBSCRIBE, email to debian-dpkg-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: