On Fri, Jan 27, 2006 at 10:19:50AM -0800, Brian Harring wrote:
#!/bin/sh
eval $(bzcat environment.bz2 | filter-env -f '.*' -v 'BASH.*' )
for __x in $@; do
echo __x=$(echo ${__x} | tr '\n,\r,\t' ' , , ')
echo ${__x}=$(echo ${!__x} | tr '\n,\r,\t' ' , , ')
done
Change above would
On Mon, 23 Jan 2006 14:08:00 -0800
Brian Harring [EMAIL PROTECTED] wrote:
On Mon, Jan 23, 2006 at 07:44:44PM +0100, Marius Mauch wrote:
On Mon, 23 Jan 2006 03:47:11 -0800
Can't follow your thinking here. As said, the code won't corrupt any
data, at worst it will tell the user that it
On Wed, 11 Jan 2006 12:39:03 -0800
Brian Harring [EMAIL PROTECTED] wrote:
Regex you've got there allows for pulling the wrong text- recall, ebd
originally was doing grep based filtering (regex). Had to rewrite
that in a major hurry since bash syntax (specifically here ops)
forces you to
On Mon, Jan 23, 2006 at 11:16:03AM +0100, Marius Mauch wrote:
On Wed, 11 Jan 2006 12:39:03 -0800
Brian Harring [EMAIL PROTECTED] wrote:
Regex you've got there allows for pulling the wrong text- recall, ebd
originally was doing grep based filtering (regex). Had to rewrite
that in a
On Tue, Jan 10, 2006 at 07:53:04PM +0100, Marius Mauch wrote:
Currently vardbapi.aux_get only works for a subset of all auxdbkeys, as
some like KEYWORDS or DESCRIPTIOn aren't stored in vdb directly.
They are however stored in environment.bz2, but not accessible
there.
This is unintuitive and
Currently vardbapi.aux_get only works for a subset of all auxdbkeys, as
some like KEYWORDS or DESCRIPTIOn aren't stored in vdb directly.
They are however stored in environment.bz2, but not accessible
there.
This is unintuitive and limits tools like equery or my own auxget
and metascan tools in
