[Dune] Re: [Dune-CVS] dune-common r4690 - trunk/bin

Christian Engwer christi at uni-hd.de
Sat Aug 12 13:19:26 CEST 2006


Hi Markus,

> Modified: trunk/bin/dunemodules.inc
> ===================================================================
> --- trunk/bin/dunemodules.inc	2006-08-11 12:48:54 UTC (rev 4689)
> +++ trunk/bin/dunemodules.inc	2006-08-11 13:38:11 UTC (rev 4690)
> @@ -83,7 +83,7 @@
>          export MODULES="$MODULES $module"
>        fi
>      done <<EOF
> - $(find "$dir" -name $CONTROL )
> + $(find "$dir" -name $CONTROL | grep -v 'dune\-[-a-zA-Z_]*\-[0-9]\+.[0-9]\+/')
>  EOF
>    else
>      if test -f "$1" && 

I'm afraid this might break some installations... Consider the case
where you download a dune-common tar ball and are writing your own
modules. Your will need to find the dune.module file in side the
extracted tar ball, in order to build your own modules, but the grep
will block your dune-common directory. I think the correct solution
would be to something like the folling pseudo code:

foreach file in ($LIST); do
  foreach entry matching "/^$(dirname $file)/"; do
    delete $entry from $LIST
  done
done

I' not shure what would be the best way to implement this in shell but
it would fix the problem of modules inside of modules (which is the
case for the make dist).

Christian




More information about the Dune mailing list