cvs commit: ALFS syntax.txt

Mark Ellis mark.uzumati at
Thu Mar 28 02:25:17 PST 2002

On 2002.03.28 00:12 Seth W. Klein wrote:
> Lee Saferite <dsaferite at> wrote:
> >
> > On Wed, 27 Mar 2002 22:42:29 +0000
> > Mark Ellis <mark.uzumati at> wrote:
> >
> > > I notice you left <command> out of <make> and <configure>. I agree
> that
> > > adding a different command to these turns them into <execute> in
> > > disguise, it might just be more self documenting to have this
> > > capability in the profile.
> >
> > I figure, if you need to do a <command>, then you should use the
> <execute> or find another way to do it.  if you have a strong enough
> set of core elements, you don't need that kind of fluff.  Sorry if I
> make anyone angry.  ;)
> I really like <command> in <configure>. It would irk me highly to have
> to use <execute> instead of <configure> just because a package uses a
> separate build directory as gcc, glibc, binutils, and e2fsprogs do.

I'd actually forgotten about those, i was thinking of stuff like perl 
that uses ./Configure or ./configure.gnu

Unsubscribe: send email to listar at
and put 'unsubscribe alfs-discuss' in the subject header of the message

More information about the alfs-discuss mailing list