Re: [fink-core] Types magic feature request

[Alexander H. <ale...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/14/11 10:37 AM, Max Horn wrote:
> 
> Am 03.11.2011 um 13:47 schrieb Alexander Hansen:
> 
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> 
>> I was thinking that it might be useful for fink to allow other
>> Types besides Type: perl, e.g. Type: python, Type: octave, etc.,
>> to have their own %{default_script} options.  There's a lot of
>> duplication of CompileScripts and InstallScripts within the
>> octave-forge modules, for example, and the python modules.
> 
>> I'd envision having the relevant interpreter packages install
>> modules within %p/lib/perl5/Fink (maybe in a
>> %p/lib/perl5/Fink/Types directory?) and have the Type handler in
>> fink check that directory for the installed plugins.  Maybe we
>> could move the Perl type handler there too.
> 
> The basic idea of supporting more languages, and doing it in a
> flexible and unified way, sounds great to me. By all means, the
> perl type handler should be unified with that, too, if at all
> possible.
> 
> But I wonder if we really need "installable plugins" for this?
> Don't get me wrong, I am not opposed, I just wonder whether it will
> be worth the extra effort...?
> 
> 
> If we allow packages to provide types, say, "Type: octave", then of
> course a package would have to bdep on the package providing this
> type.
> 
> 
> Cheers, Max
> 

My thought was to allow the maintainers of the script interpreter
packages to change _their_ scripts without having to wait for a new
Fink release.

- -- 
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7BP5cACgkQB8UpO3rKjQ9WBwCfTpLJmCyOyA+eyaTVX+mVot/s
XBAAnApHDxETQnpo++Nese251F0YoRlN
=gTTU
-----END PGP SIGNATURE-----