Re: Packaging shell functions

2008-10-09 Thread Michael Welle
Hi, Clint Adams <[EMAIL PROTECTED]> writes: > On Thu, Oct 09, 2008 at 03:04:28PM +0200, Michael Welle wrote: >> vared [1] lets you edit environment variables an a fancy way and than >> it sets their new value in your current shell session. The shell >> functions/aliases are a crude way to work ar

Re: Packaging shell functions

2008-10-09 Thread Clint Adams
On Thu, Oct 09, 2008 at 03:04:28PM +0200, Michael Welle wrote: > vared [1] lets you edit environment variables an a fancy way and than > it sets their new value in your current shell session. The shell > functions/aliases are a crude way to work around some limitations > (environment variables can

Re: Packaging shell functions

2008-10-09 Thread Michael Meskes
> I'm packaging a little tool called vared. Vared relies on some shell > functions and/or aliases that must have been sourced into the > environment before usage. What may be the best pratice to package > such shell functions? > ... How about a little wrapper setting the environment and then execu

Re: Packaging shell functions

2008-10-09 Thread Michael Welle
Hi, Michael Meskes <[EMAIL PROTECTED]> writes: >> I'm packaging a little tool called vared. Vared relies on some shell >> functions and/or aliases that must have been sourced into the >> environment before usage. What may be the best pratice to package >> such shell functions? >> ... > > How abou

Re: Packaging shell functions

2008-10-09 Thread Michael Welle
Hi, "Eugene V. Lyubimkin" <[EMAIL PROTECTED]> writes: > Michael Welle wrote: >> Hi, >> >> I'm packaging a little tool called vared. Vared relies on some shell >> functions and/or aliases that must have been sourced into the >> environment before usage. What may be the best pratice to package >>

Re: Packaging shell functions

2008-10-09 Thread Eugene V. Lyubimkin
Michael Welle wrote: > Hi, > > I'm packaging a little tool called vared. Vared relies on some shell > functions and/or aliases that must have been sourced into the > environment before usage. What may be the best pratice to package > such shell functions? I would take a look on packaging of 'app

Packaging shell functions

2008-10-09 Thread Michael Welle
Hi, I'm packaging a little tool called vared. Vared relies on some shell functions and/or aliases that must have been sourced into the environment before usage. What may be the best pratice to package such shell functions? First approch is to put the shell code somewhere under /usr/share/vared