sm-sorcery AT lists.ibiblio.org
Subject: Discussion of Sorcery related topics
List archive
- From: "Eric Sandall" <eric AT sandall.us>
- To: sm-sorcery AT lists.ibiblio.org
- Subject: Re: [SM-Sorcery] ask_enable and ask_with
- Date: Thu, 24 Apr 2003 09:15:29 -0700 (PDT)
Ladislav Hagara said:
> Howdy !!!
>
> Spells flac, sox and SDL_sound contains IMHO very useful function
> ask_enable.
> What about including ask_enable and ask_with in sorcery ?
>
> I think this were very useful for grimoire gurus.
>
> CONFIGURE could contains only:
>
> ask_enable oldrate "old rate code" "n"
> ask_enable fastulaw "fast ulaw compression (-32K memory)" "y"
> ask_with ossdsp "support for /dev/dsp (OSS)" "y"
> ask_with sunaudio "support for /dev/audio (SUN, etc)" "n"
>
> - lace -
>
>
> function ask_enable() {
> ...
> if query "Enable $2 ?" $3
> then cfg="--enable-$1"
> else cfg="--disable-$1"
> ...
> }
>
> function ask_with() {
> ...
> if query "Build with $2?" $3
> then cfg="--with-$1"
> else cfg="--without-$1"
> ...
> }
This would certainly make CONFIGURE easier to write and read, so any
future implementations could profit from this. However, we would want to
rewrite all of the CONFIGUREs which used the "old way" so as to give
examples for future spell makers. :)
I'd also like to propose a fourth ($4) optional parameter: warning. Some
spells have experimental/broken features that some people would like to
try out, and having an option to say "EXPERIMENTAL" or "BROKEN" (as the LK
does) or any other warning message.
Ex (netatalk's new CONFIGURE):
ask_enable dropkludge "the dropbox fix" " INSECURE!"
function ask_enable () {
...
if query "Enable $2${MESSAGE_COLOR}($4)${DEFAULT_COLOR}?" $3
then cfg="--enable-$1"
else cfg="--disable-$1"
...
}
Same with ask_with. I believe this would work, and if no fourth parameter
is passed, nothing would be printed in that space (note that I put the
space in the description of $4, and not in the query line, that way
[hopefully] there won't even be a space to mess the output if no fourth
parameter is passed).
-One of Four
a.k.a. sandalle
--
PGP Key Fingerprint: FCFF 26A1 BE21 08F4 BB91 FAED 1D7B 7D74 A8EF DD61
http://search.keyserver.net:11371/pks/lookup?op=get&search=0xA8EFDD61
Eric Sandall | Source Mage GNU/Linux Developer
eric AT sandall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
>From dossen AT daimi.au.dk Thu Apr 24 12:05:43 2003
Return-Path: <dossen AT daimi.au.dk>
Delivered-To: sm-sorcery AT lists.ibiblio.org
Received: from horse03.daimi.au.dk (horse03.daimi.au.dk [130.225.18.243])
by happyhouse.metalab.unc.edu (Postfix) with ESMTP id C81C020150
for <sm-sorcery AT lists.ibiblio.org>;
Thu, 24 Apr 2003 12:05:39 -0400 (EDT)
Received: (from dossen@localhost)
by horse03.daimi.au.dk (8.11.6/8.11.6) id h3OG5aL21501
for sm-sorcery AT lists.ibiblio.org; Thu, 24 Apr 2003 18:05:36 +0200
Date: Thu, 24 Apr 2003 18:05:36 +0200
From: Mads Laursen <dossen+sgl AT daimi.au.dk>
To: sm-sorcery AT lists.ibiblio.org
Subject: Re: [SM-Sorcery] ask_enable and ask_with
Message-ID: <20030424160536.GD3167 AT horse03.daimi.au.dk>
Mail-Followup-To: sm-sorcery AT lists.ibiblio.org
References: <3EA7AF1F.994EE772 AT vabo.cz>
<33777.134.121.46.137.1051200929.squirrel AT mail.sandall.us>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="XvKFcGCOAo53UbWW"
Content-Disposition: inline
In-Reply-To: <33777.134.121.46.137.1051200929.squirrel AT mail.sandall.us>
User-Agent: Mutt/1.4i
X-Operating-System: Linux horse03 2.4.18-19.7.xsmp
X-PGP-Key: https://www.daimi.au.dk/~dossen/dossen.pgp
X-Face:
(mRTl0M$hmeDo}7]hN"n8@Su?qY&}SwM-Cbc?%v'7NtBtOC3[~O7dxa)XEsy&p6'_jeC%.vf9OZ]:~32|ZAi.`C{tFu+OMb2isv_'Z|5;d:n%N+kR4XFJZj:9]/n;X?U'=m#|Ab,)Q3"{2hPSl$IdYC8[lxpYH'^4Gad8Ku&YcdU!`k'Sw~AP6QHx|x:K@h4@6~>j4hePj!&]lYyEp'G
X-BeenThere: sm-sorcery AT lists.ibiblio.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion of Sorcery related topics <sm-sorcery.lists.ibiblio.org>
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-sorcery>,
<mailto:sm-sorcery-request AT lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/sm-sorcery>
List-Post: <mailto:sm-sorcery AT lists.ibiblio.org>
List-Help: <mailto:sympa AT lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-sorcery>,
<mailto:sm-sorcery-request AT lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2003 16:05:43 -0000
--XvKFcGCOAo53UbWW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 24/04/03 09.15, Eric Sandall wrote:
>=20
> Ladislav Hagara said:
> > Howdy !!!
> >
> > Spells flac, sox and SDL_sound contains IMHO very useful function
> > ask_enable.
> > What about including ask_enable and ask_with in sorcery ?
Great idea. It might also be usefull to look at the mozilla spell, it
has something similar.
[snip]
> I'd also like to propose a fourth ($4) optional parameter: warning. Some
> spells have experimental/broken features that some people would like to
> try out, and having an option to say "EXPERIMENTAL" or "BROKEN" (as the LK
> does) or any other warning message.
Good idea.
[snip]
Another point to rememebr is persistence. The options selected should
be saved somewhere. And it might also be useful for the selections to
be accessable in BUILD (and possibly other scripts run after
CONFIGURE), once again using mozilla as an example it has options
which also require an environment variable to be set.=20
It might also be the case that some spell provides some facility, iff
it is configured with a particular option. Should there be some way to
handle that?=20
But anything to allow more configurability in the spells is a good
thing as far as I'm concerned.
/dossen
--=20
Common sense is the collection of prejudices acquired by age eighteen.
-- Albert Einstein
--XvKFcGCOAo53UbWW
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+qAtQ411kMaBbTb0RArsTAJ41d4mD2cvs+7oEMGI1DrgvzfAvRACg02M3
JeflrP0Yd/CGDgvxn3xYvE8=
=ybrs
-----END PGP SIGNATURE-----
--XvKFcGCOAo53UbWW--
>From eric AT sandall.us Thu Apr 24 12:59:21 2003
Return-Path: <eric AT sandall.us>
Delivered-To: sm-sorcery AT lists.ibiblio.org
Received: from sandall.us (a052082.dsl.fsr.net [12.32.52.82])
by happyhouse.metalab.unc.edu (Postfix) with ESMTP id 29E952001A
for <sm-sorcery AT lists.ibiblio.org>;
Thu, 24 Apr 2003 12:59:20 -0400 (EDT)
Received: from [127.0.0.1] (helo=mail.sandall.us)
by sandall.us with smtp (Exim 4.14)
id 198keO-0000cz-AP
for sm-sorcery AT lists.ibiblio.org; Thu, 24 Apr 2003 10:36:48 -0700
Received: from 134.121.46.137
(SquirrelMail authenticated user sandalle)
by mail.sandall.us with HTTP;
Thu, 24 Apr 2003 10:36:48 -0700 (PDT)
Message-ID: <34192.134.121.46.137.1051205808.squirrel AT mail.sandall.us>
In-Reply-To: <20030424160536.GD3167 AT horse03.daimi.au.dk>
References:
<3EA7AF1F.994EE772 AT vabo.cz><33777.134.121.46.137.1051200929.squirrel@m
ail.sandall.us> <20030424160536.GD3167 AT horse03.daimi.au.dk>
Date: Thu, 24 Apr 2003 10:36:48 -0700 (PDT)
Subject: Re: [SM-Sorcery] ask_enable and ask_with
From: "Eric Sandall" <eric AT sandall.us>
To: sm-sorcery AT lists.ibiblio.org
User-Agent: SquirrelMail/1.4.0
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
X-Priority: 3
Importance: Normal
X-BeenThere: sm-sorcery AT lists.ibiblio.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion of Sorcery related topics <sm-sorcery.lists.ibiblio.org>
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-sorcery>,
<mailto:sm-sorcery-request AT lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/sm-sorcery>
List-Post: <mailto:sm-sorcery AT lists.ibiblio.org>
List-Help: <mailto:sympa AT lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-sorcery>,
<mailto:sm-sorcery-request AT lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2003 16:59:22 -0000
Mads Laursen said:
<snip>
> Another point to rememebr is persistence. The options selected should
> be saved somewhere. And it might also be useful for the selections to
> be accessable in BUILD (and possibly other scripts run after
> CONFIGURE), once again using mozilla as an example it has options
> which also require an environment variable to be set.
>
> It might also be the case that some spell provides some facility, iff
> it is configured with a particular option. Should there be some way to
> handle that?
>
> But anything to allow more configurability in the spells is a good
> thing as far as I'm concerned.
>
> /dossen
The ask_*() functions should also have '>> ${SPELL_CONFIG}' at the end of
their configuration.
Ex:
function ask_enable() {
...
if query "Enable $2 ?" $3
then cfg="--enable-$1"
else cfg="--disable-$1"
echo cfg >> ${SPELL_CONFIG}
fi
...
}
As for the environment variables, we could have another function:
function ask_export() {
...
if query "Enable $2${MESSAGE_COLOR}($4)${DEFAULT_COLOR}?" $3
then export $2=$3
echo "$2=$3" >> ${SPELL_CONFIG}
fi
...
}
Not sure if that's exactly what we want, but it's the general idea. :)
Should all of these go in a libask file? ;)
What facilities are you talking about? Isn't that what the ask_*
functions do ?
-One of Four
a.k.a. sandalle
--
PGP Key Fingerprint: FCFF 26A1 BE21 08F4 BB91 FAED 1D7B 7D74 A8EF DD61
http://search.keyserver.net:11371/pks/lookup?op=get&search=0xA8EFDD61
Eric Sandall | Source Mage GNU/Linux Developer
eric AT sandall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
>From dossen AT daimi.au.dk Thu Apr 24 13:49:59 2003
Return-Path: <dossen AT daimi.au.dk>
Delivered-To: sm-sorcery AT lists.ibiblio.org
Received: from horse03.daimi.au.dk (horse03.daimi.au.dk [130.225.18.243])
by happyhouse.metalab.unc.edu (Postfix) with ESMTP id 460D120090
for <sm-sorcery AT lists.ibiblio.org>;
Thu, 24 Apr 2003 13:49:59 -0400 (EDT)
Received: (from dossen@localhost)
by horse03.daimi.au.dk (8.11.6/8.11.6) id h3OHntO29349
for sm-sorcery AT lists.ibiblio.org; Thu, 24 Apr 2003 19:49:55 +0200
Date: Thu, 24 Apr 2003 19:49:55 +0200
From: Mads Laursen <dossen+sgl AT daimi.au.dk>
To: sm-sorcery AT lists.ibiblio.org
Subject: Re: [SM-Sorcery] ask_enable and ask_with
Message-ID: <20030424174955.GF3167 AT horse03.daimi.au.dk>
Mail-Followup-To: sm-sorcery AT lists.ibiblio.org
References: <20030424160536.GD3167 AT horse03.daimi.au.dk>
<34192.134.121.46.137.1051205808.squirrel AT mail.sandall.us>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="G6nVm6DDWH/FONJq"
Content-Disposition: inline
In-Reply-To: <34192.134.121.46.137.1051205808.squirrel AT mail.sandall.us>
User-Agent: Mutt/1.4i
X-Operating-System: Linux horse03 2.4.18-19.7.xsmp
X-PGP-Key: https://www.daimi.au.dk/~dossen/dossen.pgp
X-Face:
(mRTl0M$hmeDo}7]hN"n8@Su?qY&}SwM-Cbc?%v'7NtBtOC3[~O7dxa)XEsy&p6'_jeC%.vf9OZ]:~32|ZAi.`C{tFu+OMb2isv_'Z|5;d:n%N+kR4XFJZj:9]/n;X?U'=m#|Ab,)Q3"{2hPSl$IdYC8[lxpYH'^4Gad8Ku&YcdU!`k'Sw~AP6QHx|x:K@h4@6~>j4hePj!&]lYyEp'G
X-BeenThere: sm-sorcery AT lists.ibiblio.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion of Sorcery related topics <sm-sorcery.lists.ibiblio.org>
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-sorcery>,
<mailto:sm-sorcery-request AT lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/sm-sorcery>
List-Post: <mailto:sm-sorcery AT lists.ibiblio.org>
List-Help: <mailto:sympa AT lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-sorcery>,
<mailto:sm-sorcery-request AT lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2003 17:50:00 -0000
--G6nVm6DDWH/FONJq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 24/04/03 10.36, Eric Sandall wrote:
>=20
> Mads Laursen said:
> <snip>
> > Another point to rememebr is persistence. The options selected should
> > be saved somewhere. And it might also be useful for the selections to
> > be accessable in BUILD (and possibly other scripts run after
> > CONFIGURE), once again using mozilla as an example it has options
> > which also require an environment variable to be set.
> >
> > It might also be the case that some spell provides some facility, iff
> > it is configured with a particular option. Should there be some way to
> > handle that?
> >
> > But anything to allow more configurability in the spells is a good
> > thing as far as I'm concerned.
> >
> > /dossen
>=20
> The ask_*() functions should also have '>> ${SPELL_CONFIG}' at the end of
> their configuration.
>=20
> Ex:
>=20
> function ask_enable() {
> ...
> if query "Enable $2 ?" $3
> then cfg=3D"--enable-$1"
> else cfg=3D"--disable-$1"
> echo cfg >> ${SPELL_CONFIG}
> fi
> ...
> }
>=20
> As for the environment variables, we could have another function:
>=20
> function ask_export() {
> ...
> if query "Enable $2${MESSAGE_COLOR}($4)${DEFAULT_COLOR}?" $3
> then export $2=3D$3
> echo "$2=3D$3" >> ${SPELL_CONFIG}
> fi
> ...
> }
>=20
> Not sure if that's exactly what we want, but it's the general idea. :)
>=20
> Should all of these go in a libask file? ;)
My point was that we may need to do things differently in BUILD
depending on what options where chosen, so either we do something like
if `echo $cfg|grep -q "enable-option"` ; then
something
else
somethingelse
fi=20
or we have a function that does something similar to the grep part.
The difference is that calling a function rather than spelling it out
in the BUILD script makes the intention clearer (and it may allow some
additional checks, say for both enable and with, making the spell a
little bit easier to hack/maintain (only CONFIGURE needs to know if
with or enable or some other method was used)).=20
> What facilities are you talking about? Isn't that what the ask_*
> functions do ?
What I'm considering (and this is just idle thought, no particular
spell in mind) is whether it would be proper to use the provides
function depending on a configuration?=20
For instance the 'mail' command. It is as far as I recall provided by
mutt via symlinking. There are also packages that directly install a
mail binary (not sure if we have any of them in the grimoire). Now a
spell that needs a 'mail' command would likely 'require mail' or
something like that (not at home right now), and spells like mutt
would 'provides mail', right? But what if mutt could include
'ask_export MAIL_SYMLINK "Create mail symlink?" y'
should it then provide mail?=20
And while I'm at it, is there a way to determine if some optional
dependency was chosen? Besides checking if the spell is installed? As
an example gaim has a plugin, gaim-e, which depends on gpgme. Hence
gaim optionally depends on gpgme (or did, currently I don't think
gaim-e compiles with gaim). When it becomes time to find out whether
gaim-e should be built it is decided by 'spell_installed gpgme'. To me
this seems kludgy -- what if I 'cast -r -c gaim' and select no for gaim-e?
My main point is that configurability is one of the neat things in
SMGL, and I hope we get much more of it (mostly so that I can enable
all those nifty experimental options and stuff), while still making
things work well.
/dossen
--=20
Common sense is the collection of prejudices acquired by age eighteen.
-- Albert Einstein
--G6nVm6DDWH/FONJq
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+qCPC411kMaBbTb0RAojbAJ9eKDuSUNhXD0bEgc3Kq5fbTIQglACdG4Y3
EXnetYRTBjytwL10cqtSYHc=
=kkOe
-----END PGP SIGNATURE-----
--G6nVm6DDWH/FONJq--
>From dufflebunk AT dufflebunk.homeip.net Thu Apr 24 15:33:19 2003
Return-Path: <dufflebunk AT dufflebunk.homeip.net>
Delivered-To: sm-sorcery AT lists.ibiblio.org
Received: from mail.dufflebunk.homeip.net (d57-98-11.home.cgocable.net
[24.57.98.11])
by happyhouse.metalab.unc.edu (Postfix) with ESMTP id 31E9920088
for <sm-sorcery AT lists.ibiblio.org>;
Thu, 24 Apr 2003 15:33:19 -0400 (EDT)
Received: from localhost (unknown [127.0.0.1])
by mail.dufflebunk.homeip.net (Postfix) with ESMTP
id 2919C44327; Thu, 24 Apr 2003 15:26:55 -0400 (EDT)
Subject: Re: [SM-Sorcery] ask_enable and ask_with
From: Dufflebunk <dufflebunk AT dufflebunk.homeip.net>
To: Mads Laursen <dossen+sgl AT daimi.au.dk>
In-Reply-To: <20030424174955.GF3167 AT horse03.daimi.au.dk>
References: <20030424160536.GD3167 AT horse03.daimi.au.dk>
<34192.134.121.46.137.1051205808.squirrel AT mail.sandall.us>
<20030424174955.GF3167 AT horse03.daimi.au.dk>
Content-Type: text/plain
Organization:
Message-Id: <1051212413.8508.91.camel AT dufflebunk.homeip.net>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4
Date: 24 Apr 2003 15:26:54 -0400
Content-Transfer-Encoding: 7bit
cc: sm-sorcery <sm-sorcery AT lists.ibiblio.org>
X-BeenThere: sm-sorcery AT lists.ibiblio.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion of Sorcery related topics <sm-sorcery.lists.ibiblio.org>
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-sorcery>,
<mailto:sm-sorcery-request AT lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/sm-sorcery>
List-Post: <mailto:sm-sorcery AT lists.ibiblio.org>
List-Help: <mailto:sympa AT lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-sorcery>,
<mailto:sm-sorcery-request AT lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2003 19:33:19 -0000
See comments below...
On Thu, 2003-04-24 at 13:49, Mads Laursen wrote:
> On 24/04/03 10.36, Eric Sandall wrote:
> >
> > Mads Laursen said:
> > <snip>
> > > Another point to rememebr is persistence. The options selected should
> > > be saved somewhere. And it might also be useful for the selections to
> > > be accessable in BUILD (and possibly other scripts run after
> > > CONFIGURE), once again using mozilla as an example it has options
> > > which also require an environment variable to be set.
> > >
> > > It might also be the case that some spell provides some facility, iff
> > > it is configured with a particular option. Should there be some way to
> > > handle that?
> > >
> > > But anything to allow more configurability in the spells is a good
> > > thing as far as I'm concerned.
> > >
> > > /dossen
> >
> > The ask_*() functions should also have '>> ${SPELL_CONFIG}' at the end of
> > their configuration.
> >
> > Ex:
> >
> > function ask_enable() {
> > ...
> > if query "Enable $2 ?" $3
> > then cfg="--enable-$1"
> > else cfg="--disable-$1"
> > echo cfg >> ${SPELL_CONFIG}
> > fi
> > ...
> > }
> >
> > As for the environment variables, we could have another function:
> >
> > function ask_export() {
> > ...
> > if query "Enable $2${MESSAGE_COLOR}($4)${DEFAULT_COLOR}?" $3
> > then export $2=$3
> > echo "$2=$3" >> ${SPELL_CONFIG}
> > fi
> > ...
> > }
> >
> > Not sure if that's exactly what we want, but it's the general idea. :)
> >
> > Should all of these go in a libask file? ;)
I would prefer to put them in a new libconfigure
> My point was that we may need to do things differently in BUILD
> depending on what options where chosen, so either we do something like
>
> if `echo $cfg|grep -q "enable-option"` ; then
> something
> else
> somethingelse
> fi
>
> or we have a function that does something similar to the grep part.
> The difference is that calling a function rather than spelling it out
> in the BUILD script makes the intention clearer (and it may allow some
> additional checks, say for both enable and with, making the spell a
> little bit easier to hack/maintain (only CONFIGURE needs to know if
> with or enable or some other method was used)).
>
> > What facilities are you talking about? Isn't that what the ask_*
> > functions do ?
>
> What I'm considering (and this is just idle thought, no particular
> spell in mind) is whether it would be proper to use the provides
> function depending on a configuration?
Optional provides would be very messy. It would make searching the
grimoire for what can provide a service nearly impossible.
>
> For instance the 'mail' command. It is as far as I recall provided by
> mutt via symlinking. There are also packages that directly install a
> mail binary (not sure if we have any of them in the grimoire). Now a
> spell that needs a 'mail' command would likely 'require mail' or
> something like that (not at home right now), and spells like mutt
> would 'provides mail', right? But what if mutt could include
> 'ask_export MAIL_SYMLINK "Create mail symlink?" y'
> should it then provide mail?
>
> And while I'm at it, is there a way to determine if some optional
> dependency was chosen? Besides checking if the spell is installed? As
> an example gaim has a plugin, gaim-e, which depends on gpgme. Hence
> gaim optionally depends on gpgme (or did, currently I don't think
> gaim-e compiles with gaim). When it becomes time to find out whether
> gaim-e should be built it is decided by 'spell_installed gpgme'. To me
> this seems kludgy -- what if I 'cast -r -c gaim' and select no for gaim-e?
Yes, check the OPTS to see if the enable switch is there.
>
> My main point is that configurability is one of the neat things in
> SMGL, and I hope we get much more of it (mostly so that I can enable
> all those nifty experimental options and stuff), while still making
> things work well.
However, the ease of making spells is also one of the great things.
Adding too many options and stuff can make making spells more complex.
>
> /dossen
-
[SM-Sorcery] ask_enable and ask_with,
Ladislav Hagara, 04/24/2003
- Re: [SM-Sorcery] ask_enable and ask_with, Eric Sandall, 04/24/2003
- <Possible follow-up(s)>
- Re: [SM-Sorcery] ask_enable and ask_with, Ladislav Hagara, 04/25/2003
- Re: [SM-Sorcery] ask_enable and ask_with, Eric Sandall, 04/25/2003
Archive powered by MHonArc 2.6.24.