search for: get_packag

...Content-type: text/x-diff; charset="us-ascii"; name="INSTALL.patch" Content-disposition: attachment; filename="INSTALL.patch" Content-transfer-encoding: 7bit *** INSTALL~ Wed Jun 22 11:09:59 2005 --- INSTALL Fri Dec 2 17:08:50 2005 *************** *** 127,136 **** get_packages () { ## get the full path names to all packages contained in $1. ## NOTE: modifies pkgs! if grep "^Contains:" "${1}/DESCRIPTION" >/dev/null; then bundlepkg=`get_dcf_field Contains "${1}/DESCRIPTION"` for p in ${bundlepkg}; do ! pkgs=&...

...uot;us-ascii"; name="INSTALL.patch" > Content-disposition: attachment; filename="INSTALL.patch" > Content-transfer-encoding: 7bit > > *** INSTALL~ Wed Jun 22 11:09:59 2005 > --- INSTALL Fri Dec 2 17:08:50 2005 > *************** > *** 127,136 **** > get_packages () { > ## get the full path names to all packages contained in $1. > ## NOTE: modifies pkgs! > if grep "^Contains:" "${1}/DESCRIPTION" >/dev/null; then > bundlepkg=`get_dcf_field Contains "${1}/DESCRIPTION"` > for p in ${bundlepkg...

...y unreachable for me) doesn't do it. > Our philosphy is to assume that the users tools are standard (e.g. POSIX) > unless there is widespread evidence to the contrary. The INSTALL.in script already contains various '> /dev/null'; my patch just adds another two, inside the get_packages function, just to avoid any output that the cd-command might happen to have. I would not have thought this to be so controversial. Regards, Philip -- Philip Lijnzaad Genomics Laboratory Dept. of Biomedical Genetics Univer...