Hello,
Could someone with CVS write access (Bill?) commit the attached files to 7.6/packaging/fink, so that fink users could try the new package version?
Fink users, see url:http://bertrand.gotpike.org/ for more informations.
Thanx in advance.
Why the license change?
Because the package validator complained about the old one.
License recognized by the package validator: <ur:http://fink.sourceforge.net/doc/packaging/policy.php? phpLang=en#licenses>
If you feel mentioning MPL is important, it could be discussed on the fink mailing list.
You can probably use this one for simplicity:
"OSI-Approved - for other Open Source licenses approved by the Open Source Initiative. One of OSI's requirements is that free distribution of binaries and sources is allowed. This value can also be used as an umbrella for dual-licensed packages."^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
GPL, LGPL and MPL are all on OSI:s list of approved licenses.
"OSI-Approved - for other Open Source licenses approved by the Open Source Initiative. One of OSI's requirements is that free distribution of binaries and sources is allowed. This value can also be used as an umbrella for dual-licensed packages."^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
GPL, LGPL and MPL are all on OSI:s list of approved licenses.
I'll use that.
-- Bertrand LUPART Linkeo.com | http://www.linkeo.com +33 1 72 71 71 84 | 17, rue de la Banque - F75002 Paris
Another question; Why are you adding so many configure options yourself? I can see why you would like to turn off some things like GTK, postgres and GL, but why forcefully add modules and features? Why turn off optimizations? The point with a configure script is that it should make the configurations based on how the system looks. You should only need to add a configure argument if the configure tests are flawed, and even then it is preferred that you let us know so we can fix the tests instead.
Another question; Why are you adding so many configure options yourself? I can see why you would like to turn off some things like GTK, postgres and GL, but why forcefully add modules and features? Why turn off optimizations? The point with a configure script is that it should make the configurations based on how the system looks.
These configure options are mainly there because this info file is based on someone else's work.
Anyhow, the CompileScript line should be tidied up now. I'm currently looking at it. Re-enabling optimizations shows quite a great speedup with pike -x benchmark.
These info/patch files are still work in progress, don't expect them in a final state for now. I just want to share them with other fink users for having some feedback.
You should only need to add a configure argument if the configure tests are flawed, and even then it is preferred that you let us know so we can fix the tests instead.
True.
What about merging the include_prefix patch into Pike? Both Debian and Fink use it. It could be usefull for others.
pike-devel@lists.lysator.liu.se