Request for comments: General solution for name space pollution issues
Hi,
I suggested some solution for cases when we are facing name space
pollution[1] on Debian Med list but did not got really helpfull answers.
There was actually one (full quoted below) which considered the method
as not acceptable but even when asking explicitely Julien did not gave
any reasons for his opinion.
Any further remarks from a more general audience?
Kind regards
Andreas.
----- Forwarded message from Julien Cristau <jcristau@debian.org> -----
Date: Tue, 15 May 2012 13:57:08 +0200
From: Julien Cristau <jcristau@debian.org>
To: Andreas Tille <andreas@an3as.eu>
Cc: 661519@bugs.debian.org,
Debian Med Project List <debian-med@lists.debian.org>
Subject: Re: General solution for name space pollution issues
On Tue, May 15, 2012 at 13:42:38 +0200, Andreas Tille wrote:
> For the moment I would like to draw your attention to the
> other part of the solution I would like to suggest:
>
> Tweaking the PATH for Debian Med users:
>
> 1. Make paml Depends: med-config
> 2. Let med-config drop a script in /etc/profile.d which
> sets PATH="/usr/lib/debian-med/bin:$PATH"
> if debconf question "Do you want to prefer Debian Med
> executables prefered over other ones <bla bla - give
> reasons + warning>"
>
> So if the local admin answers this question with yes all original
> executable names will be restored fully transparently for the user. I
> would like to implement this before the Freeze and we should try to
> update as much relevant packages as possible following this scheme.
>
> Perhaps it makes sense to find a common way what symlinks / wrapper
> to use in /usr/bin but this is a separate decision which is somehow
> orthogonal to the solution to move all name space pollution affected
> executables to /usr/lib/debian-med/bin.
>
> What do you think?
>
I think it's both overengineered and not an acceptable solution, fwiw.
Cheers,
Julien
----- End forwarded message -----
[1] http://lists.debian.org/debian-med/2012/05/msg00042.html
--
http://fam-tille.de
Reply to: