Re: untouched bug in less package

2007-10-27 Thread Kristian Erik Hermansen 
On 10/27/07, Fergal Daly [EMAIL PROTECTED] wrote:
 The basic problem is that lesspipe uses $SHELL to tell what the
 current shell is, but that's wrong, it only tells you what the login
 shell is when what you really want to know is which shell invoked
 lesspipe.

 I'm not sure there is a way to discover what invoked you, so maybe the
 invoker needs to pass that information, maybe set $SHELL for the eval.

 Any comments?

I don't know if this is something close to what you want, but how about?
$ readlink /proc/$$/exe

Or replace $$ with the invoking pid of your lesspipe process...
-- 
Kristian Erik Hermansen

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Checking /usr/local/ before upgrading

2007-10-27 Thread Reinhard Tartler 
Vincenzo Ciancia [EMAIL PROTECTED] writes:

 Similar issues might happen if one has something in /usr/local/bin, so
 wouldn't it be wise to ask, in the upgrade program, if user wants to
 temporarily rename /usr/local to /usr/local.upgraded during upgrade, so
 things are safer? 

Isn't your email/request rather a pretty good example why installing
software to /usr/local is a bad idea wrt to system upgrades?

I'd really suggest to install your special libraries, local software
etc. either to /usr/local/$PACKAGE or /srv/local/$PACKAGE or somewhere
else. You can use environment variables or rpath to make them work.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Checking /usr/local/ before upgrading

2007-10-27 Thread Fergal Daly 
On 27/10/2007, Reinhard Tartler [EMAIL PROTECTED] wrote:
 Vincenzo Ciancia [EMAIL PROTECTED] writes:

  Similar issues might happen if one has something in /usr/local/bin, so
  wouldn't it be wise to ask, in the upgrade program, if user wants to
  temporarily rename /usr/local to /usr/local.upgraded during upgrade, so
  things are safer?

 Isn't your email/request rather a pretty good example why installing
 software to /usr/local is a bad idea wrt to system upgrades?

 I'd really suggest to install your special libraries, local software
 etc. either to /usr/local/$PACKAGE or /srv/local/$PACKAGE or somewhere
 else. You can use environment variables or rpath to make them work.

So when should anything go in /usr/local?

http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit

contains this paragraph

However, because /usr/local and its contents are for exclusive use of
the local administrator, a package must not rely on the presence or
absence of files or directories in /usr/local for normal operation.

You can find another thread on this subject (started by me) here

https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2007-May/000857.html

Basically if the system tools are going to include /usr/local in their
bin and library search paths then /usr/local is pointless. Anything
that you put in there must have identical behaviour to the /usr
version, but why would you install it if it's behaviour wasn't
different?

F

 --
 Gruesse/greetings,
 Reinhard Tartler, KeyID 945348A4

 --
 Ubuntu-devel-discuss mailing list
 Ubuntu-devel-discuss@lists.ubuntu.com
 Modify settings or unsubscribe at: 
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss