-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/10/10 8:39 PM, Chip G. wrote:
> Thanks Alexander and Martin for your replies.
>
> On Jan 7, 2010, at 14:56, Alexander Hansen wrote:
>
>> Don't bother emailing the maintainer, since this is the _intended_ behavior.
>> We have separate automake1.5 ... automake1.11 packages for packages that
>> need particular automake versions to build.
>
> This is a shame but I understand. It's hard to believe that a single product
> could have so many incompatible versions. It's also a shame that it must be
> installed and reinstalled so many times. Fortunately it's a fairly quick
> build.
>
>> The best solution is for you to do something on _your_ end, such as to
>> include
>>
>> fink install automake1.9
>>
>> as part of your automatic update script.
>
> This is extremely do-able. I use a bash script to complete the process anyway
> (backup pieces, CVS update, bootstrap, configure, make, install, etc). So
> adding this to the process will be very easy. Thanks for the idea.
>
>> Either that, or perhaps you can reconfigure your build not to use Fink's
>> automake at all, and instead to use the system's (unless your system's
>> automake is too new for your package--since you didn't provide that
>> information, I've got no idea what you have built-in) via appropriate
>> configure flags.
>
> I don't know how to do this. It is a public package available to hams
> everywhere, so I don't control the code or the config files. It's easier to
> do your first suggestion than to tweak the config each time I do an update
> (pretty regular). The program isn't too picky as it will compile with several
> versions of automake. It won't work with v1.5, however, so I will recommend
> that perhaps they check for that.
>
If the package uses the semi-standard "./configure ; make ; make
install" scheme, then you may be able just to feed an argument to
configure to change the behavior. If it does use "configure", you can
try using
./configure --help
to see what arguments it supports.
> On Jan 8, 2010, at 05:04, Martin Costabel wrote:
>
>> If certain dev packages like automake1.9 are really essential for your work,
>> you could make a little private Fink package like the one below that does
>> nothing else than prevent fink from removing these packages during its
>> normal update procedure.
>>
>> Then while you are working on your stuff, you would have the package
>> keepmydevs installed, which will make "fink update" crash whenever it tries
>> to remove automake1.9. And if you want fink update to succeed, you would
>> first remove keepmydevs and refrain from updating your own stuff during that
>> time.
>
> Where would I put this package info/file?
>
>
> --
> Chip
>
>
The local tree (/sw/fink/10.4/local/main/finkinfo)
- --
Alexander Hansen
Fink User Liaison
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAktKincACgkQB8UpO3rKjQ8VtgCeIGJo32eeWUfsciKry/V4PHHS
eRMAn1F4+U/SjghqYko7XvPIDCwrMKPr
=chpQ
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Fink-beginners mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.beginners
