-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jan 5, 2006, at 3:01 AM, Trevor Harmon wrote:
On Jan 4, 2006, at 12:37 PM, Jean-François Mertens wrote:
Careful though not to automatically add -e to a patchscript
beginning eg with
#!/usr/bin/perl
Should fink know about all possible interpreters ?
I think it should, yes. There are only a few possible shells, so
hardcoding them shouldn't be a big deal. Even if it misses one or
two, I think it would still have a higher success rate than relying
on package maintainers.
I am against this. If policy says the -e is needed, and a package
doesn't, it's a bug. Trying to fix it with a fink flag will just
cause confusion.
What happens when some people use -e, or -xe, etc.? I say filing a
bug is enough.
- -chris zubrzycki
- - --
PGP public key: http://homepage.mac.com/beren/publickey.txt
ID: 0xA2ABC070
Fingerprint: 26B0 BA6B A409 FA83 42B3 1688 FBF9 8232 A2AB C070
========================================================
ICBM Address: 39.795906N -75.056029W
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)
Comment: Please sign reply-http://www.gnupg.org
iEYEARECAAYFAkO93vAACgkQ+/mCMqKrwHDz8gCeMG/P5Urf5c778wcu9lenx2PW
GBMAoJR5VXrx99c2pqKFeuQMpnp5JNsz
=Ug7w
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
