Re: [Fink-devel] finkproject home page SL message
I recovered from it, but it took six hours of ranting and raving and a bit of recompiling. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Roll my own binary package
I would like to make the application available through fink, i.e. fink install myapp should work. My application uses components, which have GPL2, GPL, BSD and MIT licenses. Looking at the packaging instructions, it seems that I would have to have one license under which the application is released. If I cannot resolve the license issues to the satisfaction of the Fink distribution approval process, I was thinking that I could just release the binary distribution for now and release the source distribution after verifying the license stuff. Thanks. Saadat. On Fri, Sep 4, 2009 at 6:03 PM, monipol moni...@gmx.com wrote: On 04/09/2009, at 21:11, Saadat wrote: I am looking for information on how to properly build and deploy a binary package using fink. I've looked at the documentation and the FAQs, but am still unsure of what constitutes a good fink binary package. Fink provides the infrastructure for building packages from source and installing binary packages via Debian-based (dpkg, APT) tools. Usually maintainers submit package descriptions -- which contain instructions on how to fetch source code, build it, install it -- that are incorporated into Fink's distribution after approval. I'm not sure I understand your request correctly. Do you want to provide a binary package that can be installed via Fink but is not present in Fink's distributions? If so, you need to write a package description and make sure that every dependency is available either in Fink or by your own means. You would also need to provide binary packages for every combination of architecture (ppc, i386, x86_64) and most possibly operating system version (OS X 10.4, 10.5, 10.6) you want to support. You would also need to give users specific instructions on how to install this package of yours because it won't be readily available as other packages present in Fink's distributions. Note that if you write a package description and submit it to Fink then it might (after validation) be part of Fink itself, relieving you from the burden of providing specific instructions on how to install your package and making it available to other users. Cheers, -- monipol http://finkers.wordpress.com -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] finkproject home page SL message
monipol wrote: On 04/09/2009, at 22:41, Alexander Hansen wrote: Jack Howarth wrote: Shouldn't the Snow Leopard information on the finkproject home page be updated to tell folks if they had Xquartz 2.3.3.2 installed on their Leopard machine that a clean installation of fink will be required after upgrading to Snow Leopard? Just checking in about this. It looks like the 10.5.X/Xquartz-2.4.0 upgrade path is definitely hosed. If we're 100% sure that Xquartz = 2.3.3.2 will upgrade properly, then we probably should indeed amend the news item accordingly. On the other hand, if we're not sure, perhaps we should just tell anybody who's ever used Xquartz to do a clean install, just in case. I second that. I’m not sure about specific versions of Xquartz, but at any rate we’re getting more users with problems in this 10.5/Xquartz -- 10.6 upgrade path: /usr/lib/X11/libfontconfig.1.dylib has compatibility version 6.0.0 on 10.5.8, latest Xquartz whilst on 10.6 its compatibility version is 5.0.0. I do believe we should have a note about this situation on Fink's Web site. There are several different problems. One is the library versions: This is *only* a problem when upgrading from xquartz-2.4.0 to SL. The previous xquartz release 2.3.3.2 is lower than SL's X11, which is 2.3.4. But downgrading xquartz before upgrading to SL is not a solution. If any X11-using Fink packages were built while xquartz-2.4.0 was installed, it is too late. Waiting for an xquartz-2.4.x upgrade for Snow Leopard is not a solution, either: First of all, such an upgrade is not expected before next December, and secondly, the future xquartz upgrades for SL will be installed somewhere else than /usr/X11. This means that they will not - as was the main job of the xquartz upgrades until now - be useful as bug fixes for Apple's official X11. They will only be meant for people wanting to follow the bleeding edge in X11 development. (The last fasentencect is not an official xquartz declaration, but it is the logical conclusion from the currently available declarations.) The other problem is the missing *.la files. This hits everyone upgrading Fink to SL, even outside of X11. As I said repeatedly, FINK MUST PROPOSE A SOLUTION TO THIS PROBLEM, otherwise the upgrade path to 10.6 is DEAD. -- Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] finkproject home page SL message
Martin Costabel wrote: [] (The last fasentencect is not an official xquartz declaration, but it is the logical conclusion from the currently available declarations.) Read fact or sentence, as you wish. Anyway, I think it is true :-) -- Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Roll my own binary package
On 05/09/2009, at 03:34, Saadat wrote: I would like to make the application available through fink, i.e. fink install myapp should work. As I said before (and now with pointers to further information), you may: a) Submit a package description to Fink. If it conforms to Fink's policy it will eventually be part of Fink's distribution and users will be able to install it in the same manner they already do with other packages. b) Provide a package description file (.info, and .patch if necessary) and ask users to install it on their local tree [1]. This will allow users to build it from source and install it. You'll need to set up some mechanism so that users get updates of your package description file. c) Provide both a package description file, and binary .deb packages for the combinations of architecture and OS X version of your user base. When users run 'fink install yourpkg' it won't be built from source as it's already available as a binary package. The binary .deb packages must be available via an APT repository you'd need to set up. Ask users to install the package description on their local tree [1] and configure their installations to use your APT repository [2]. You'll also need to set up some mechanism so that users get updates of your package description file. [1] http://finkers.wordpress.com/2009/06/08/local-packages/ [2] http://finkers.wordpress.com/2009/06/01/fink-and-binary-distributions/ As you may see, the first option seems to be the simplest. I also know of one university department that was willing to set up their own restricted, local APT repository for their students but I'm not sure if they ended up doing this. Another university, Tokyo U., decided to submit (a subset of?) their packages to Fink and provide an APT repository that can be used by every Fink user. My application uses components, which have GPL2, GPL, BSD and MIT licenses. Looking at the packaging instructions, it seems that I would have to have one license under which the application is released. If I cannot resolve the license issues to the satisfaction of the Fink distribution approval process, I was thinking that I could just release the binary distribution for now and release the source distribution after verifying the license stuff. As Martin's already said, you may use the umbrella OSI-Approved licence if every licence is in fact approved by OSI [3]. On the other hand, can't these components be separate packages? If they're libraries we prefer they're packaged separately. That helps with licencing (using a more specific licence rather than OSI-approved), upgrading (users won't have to rebuild the whole package if there's only been a change in one of the libraries), and reuse (other packages that want to use that library can just reuse the one that's already installed). [3] http://www.opensource.org/licenses/alphabetical On Fri, Sep 4, 2009 at 6:03 PM, monipol moni...@gmx.com wrote: On 04/09/2009, at 21:11, Saadat wrote: I am looking for information on how to properly build and deploy a binary package using fink. I've looked at the documentation and the FAQs, but am still unsure of what constitutes a good fink binary package. Fink provides the infrastructure for building packages from source and installing binary packages via Debian-based (dpkg, APT) tools. Usually maintainers submit package descriptions -- which contain instructions on how to fetch source code, build it, install it -- that are incorporated into Fink's distribution after approval. I'm not sure I understand your request correctly. Do you want to provide a binary package that can be installed via Fink but is not present in Fink's distributions? If so, you need to write a package description and make sure that every dependency is available either in Fink or by your own means. You would also need to provide binary packages for every combination of architecture (ppc, i386, x86_64) and most possibly operating system version (OS X 10.4, 10.5, 10.6) you want to support. You would also need to give users specific instructions on how to install this package of yours because it won't be readily available as other packages present in Fink's distributions. Note that if you write a package description and submit it to Fink then it might (after validation) be part of Fink itself, relieving you from the burden of providing specific instructions on how to install your package and making it available to other users. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
Re: [Fink-devel] Roll my own binary package
On Sep 5, 2009, at 6:33 AM, monipol wrote: On 05/09/2009, at 03:34, Saadat wrote: My application uses components, which have GPL2, GPL, BSD and MIT licenses. Looking at the packaging instructions, it seems that I would have to have one license under which the application is released. If I cannot resolve the license issues to the satisfaction of the Fink distribution approval process, I was thinking that I could just release the binary distribution for now and release the source distribution after verifying the license stuff. As Martin's already said, you may use the umbrella OSI-Approved licence if every licence is in fact approved by OSI [3]. On the other hand, can't these components be separate packages? If they're libraries we prefer they're packaged separately. That helps with licencing (using a more specific licence rather than OSI-approved), upgrading (users won't have to rebuild the whole package if there's only been a change in one of the libraries), and reuse (other packages that want to use that library can just reuse the one that's already installed). I have two further comments on this issue. (1) The fink project is fundamentally a source-based software distribution, with binaries provided as a courtesy to users (if the fink project team has time to produce them). The only way to start out distributing in binary-only form is to distribute fink- compatible .deb files through some other channel (such as your own website). But notice that both GPL2 and GPL3 then require that this other channel provide the source to the packages, including any modifications you made to get it to compile or to customize it for your situation. So you won't have gained anything in the process. (2) Software which combines GPL2 or GPL3-licensed components with other, compatible, open-source-licensed components should use License: GPL2 or License: GPL3 as the fink license. The reasoning is that the GPL is the most restrictive of the open licenses, by requiring (rather than just allowing) source distribution, so the entire package is going to be bound by the terms of the GPL. The Free Software Foundation has a webpage listing the GPL-compatible licenses. -- Dave -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] unzip-6.0/zip-3.0 revisited
On Fri, Sep 04, 2009 at 07:03:26PM -0400, Jack Howarth wrote: I've looked through the sources for zip 3.0 and unzip 6.0 and my initial impressions appear to be borne out. They use a weird custom configure script in concert with Makefile to find the system bzip2 library on MacOS X without providing an easy way to redirect the the location of bzip2. We would have to hack up their configure script to cause it to look in %p/include. It also seems to want to use the static libbzip2 in cases other than darwin (which we don't have in our bzip2 package). The only other alternative would be to have the zip and unzip package download the bzip2 sources in the build directory and use a locally built copy of libbzip2.a. None of these solutions really seem worth the effort since it is entirely unproven that using the system bzip2 will cause us problems. Martin has already explained one reason. And I explained a second earlier. The problem isn't so much using system as using BCon. dan -- Daniel Macks dma...@netspace.org http://www.netspace.org/~dmacks -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] updates to stable
If any issues arise from the updates into stable from unstable that I've added, please cc me directly if you post to the list. I'm a tad distracted at the moment trying to get some recent major regressions on x86_64-apple-darwin addressed in gcc trunk (gcc 4.5)... http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41260 FYI, Jack -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] unzip-6.0/zip-3.0 revisited
Daniel, Actually if you look closely at the zip-3.0-1 and unzip-6.0-1 builds they never include a -I%p/include or -L%p/lib so we can just drop the BuildConflicts entirely. gzip -dc /sw/src/zip30.tgz | /sw/bin/tar -xf - --no-same-owner --no-same-permissions make -f unix/Makefile generic sh unix/configure cc -I. -DUNIX Check C compiler type (optimization options) GNU C (-O3) Check bzip2 support Check for bzip2 in bzip2 directory Check if OS already has bzip2 library installed -- OS supports bzip2 - linking in bzip2 Check for the C preprocessor Check if we can use asm code Check for ANSI options Check for prototypes Check the handling of const Check for time_t Check for size_t Check for off_t Check size of UIDs and GIDs (Now zip stores variable size UIDs/GIDs using a new extra field. This tests if this OS uses 16-bit UIDs/GIDs and so if the old 16-bit storage should also be used for backward compatibility.) s.st_uid is 4 bytes s.st_gid is 4 bytes -- UID not 2 bytes - disabling old 16-bit UID/GID support Check for Large File Support off_t is 8 bytes -- yes we have Large File Support! Check for wide char support -- have wchar_t - enabling Unicode support Check for gcc no-builtin flag Check for rmdir Check for strchr Check for strrchr Check for rename Check for mktemp Check for mktime Check for mkstemp Check for memset Check for memmove Check for strerror Check for errno declaration Check for directory libraries Check for readlink Check for directory include file Check for nonexistent include files Check for term I/O include file Check for valloc Check for /usr/local/bin and /usr/local/man Check for OS-specific flags Check for symbolic links eval make -f unix/Makefile zips `cat flags` cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H zip.c zip.c: In function 'help_extended': zip.c:1031: warning: format not a string literal and no format arguments zip.c: In function 'version_info': zip.c:1228: warning: format not a string literal and no format arguments cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H zipfile.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H zipup.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H fileio.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H util.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H globals.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H crypt.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H ttyio.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H unix/unix.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H crc32.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H zbz2err.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H deflate.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H trees.c cc -o zip zip.o zipfile.o zipup.o fileio.o util.o globals.o crypt.o ttyio.o unix.o crc32.o zbz2err.o deflate.o trees.o -Wl,-search_paths_first -lbz2 cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H zipcloak.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H -DUTIL -o zipfile_.o zipfile.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H -DUTIL -o fileio_.o fileio.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H -DUTIL -o util_.o util.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H -DUTIL -o unix_.o unix/unix.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H -DUTIL -o crc32_.o crc32.c cc -c -I. -DUNIX -O3 -DBZIP2_SUPPORT -DUIDGID_NOT_16BIT -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DHAVE_DIRENT_H -DHAVE_TERMIOS_H -DUTIL -o crypt_.o crypt.c cc -o zipcloak
[Fink-devel] gcc44 in stable needs
Hi folks: I started a clean stable 64-bit for 10.6 for purposes of testing migration of some of my packages to stable. Although gcc44 is in stable, its dependency libmpfr1 is not, so gcc44 won't build in stable. HTH, Bill William G. Scott Contact info: http://chemistry.ucsc.edu/~wgscott/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] stable wish list: fftw, swig, pygtk2-gtk-py2 and its dep.
I'm trying to migrate coot to stable, but several dependencies are in unstable, so if there is any change of migrating these, I can verify they work: These include current or recent versions (see below) of: fftw, swig, pygtk2-gtk-py26 and atk1 freetype219 glib2 (dev) gtk+2 libffi libglade2 libmpfr1 (needed for gcc44) libpng3 pango1-xft2-ft219 pycairo-py (26) pygobject2-py (26) pygtk2-gtk-py (26) scipy-core-py (26) Most are dependencies for pygtk2-gtk-py: atk1-shlibs (= 1.26.0-1) for package pygtk2-gtk-py26-2.15.2-1 glib2-dev (= 2.20.0-1) for package atk1-1.26.0-2 freetype219-shlibs (= 2.3.8-2) for package pygtk2-gtk-py26-2.15.2-1 gtk+2-shlibs (= 2.16.0-1) for package pygtk2-gtk-py26-2.15.2-1 pango1-xft2-ft219 (= 1.24.0-1) for package gtk+2-2.16.6-1 libpng3 (= 1:1.2.35-2) for package gtk+2-2.16.6-1 libglade2-shlibs (= 2.6.4-1) for package pygtk2-gtk-py26-2.15.2-1 scipy-core-py26 for package pygtk2-gtk-py26-2.15.2-1 pycairo-py26 (= 1.8.4-1) for package pygtk2-gtk-py26-2.15.2-1 pygobject2-py26 (= 2.18.0-1) for package pygtk2-gtk-py26-2.15.2-1 -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] gcc44 in stable needs
Fixed. -- Dave On Sep 5, 2009, at 5:23 PM, William G. Scott wrote: Hi folks: I started a clean stable 64-bit for 10.6 for purposes of testing migration of some of my packages to stable. Although gcc44 is in stable, its dependency libmpfr1 is not, so gcc44 won't build in stable. HTH, Bill William G. Scott Contact info: http://chemistry.ucsc.edu/~wgscott/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] stable wish list: fftw, swig, pygtk2-gtk-py2 and its dep.
On Sat, Sep 05, 2009 at 02:39:43PM -0700, William G. Scott wrote: I'm trying to migrate coot to stable, but several dependencies are in unstable, so if there is any change of migrating these, I can verify they work: These include current or recent versions (see below) of: pygtk2-gtk-py26 atk1 freetype219 glib2 (dev) gtk+2 You're asking for gnome2.26, which will migrate as the whole suite of gnome libs and related packages:) That's waiting on resolution of a bit of dbus behavior annoyance: some gnome daemons do not autostart properly. If dbus gets fixed soon, gnome simply gets a tweaked set of dependencies to take advantage of it, and then move to stable. If it does't get fixed within a week or three, it'll go to stable as-is (it's well tested in unstable) and we'll just live with users having to start some things manually if they really want them. dan -- Daniel Macks dma...@netspace.org http://www.netspace.org/~dmacks -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] swig from unstable to stable
I second the call for swig to be moved from unstable to stable so that it will build on 10.6. The pymol-py packaging currently moved from unstable won't build on 10.6 without that. I could variant pymol-py and use the system swig for 10.6 but it seems silly to have to resort to that. Jack -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Stable (almost complete) wish list
Hello, all. As previously announced by David R. Morrison, the stable tree has been pruned for Snow Leopard. Many packages aren't available and William G. Scott has already posted a wish list. :) I've gathered the last commit messages on the stable tree and I've built up a page on our wiki trying to show what's blocking what in a hierarchical fashion. It's not perfect because some packages have more than one restriction, I think I might have missed a couple of commit messages, and I haven't dug into what .info provides exactly what package, but it should give a good enough guide and overview of the work that needs to be done on stable. Having said that, here's the URL: http://wiki.finkproject.org/index.php/Fink:SnowLeopard If you have a package on _unstable_ that is known to work on x86_64 / 10.6, please verify what's necessary to move it to stable (don't forget to check dependencies). I'll keep my eye on commit logs to the stable tree and update that page accordingly. If none of your packages are listed there and you have time to work on the issues, help is more than welcome. If you don't have Snow Leopard yet (as myself) you may help with 64-bit (x86_64) Fink on OS 10.5. Cheers, -- monipol http://finkers.wordpress.com -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fink-devel@lists.sourceforge.net
Regarding the list at http://wiki.finkproject.org/index.php/Fink:SnowLeopard, the g95 package will almost certainly have to be left marked as Distribution restricted to 10.4 and 10.5. The g95 author forked long ago from FSF gcc's gfortran code and still uses an ancient version of gcc for his backend. There really isn't a major reason to use g95 in 10.6 as Apple addressed the blockdata issue which prevented ncarg from building with gfortran in Xcode 3.2. Also, g95 doesn't use a testsuite so upgrading it is always Russsian roulette in terms of its code generation. At least with FSF gcc, one knows the level of breakage when it is released. Jack ps Also if you look at the nightly Polyhedron 2005 benchmarks... http://users.physik.fu-berlin.de/~tburnus/gcc-trunk/benchmark/ g95 is the worst for code optimization. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] zsh as shell in compilescript on 10.6 breaks 32bit Fink
Martin, Regarding your question about how to get gfortran to accept the -arch option, it can't. That is an enhancement that Apple added to their gcc which wasn't (and is unlikely to ever be) ported to FSF gcc. The approach FSF gcc uses (which we have supported since I assumed maintainership) is a 64-bit (for powerpc/i386) or 32-bit (for x86_64) multilib. If you build gcc44 under x86_64, it is built as a x86_64 native compiler (which executes and generates 64-bit code as the default). If you want to generate 32-bit code with this compiler, you pass it -m32 just like our compiler wrappers do with the Snow Leopard compilers. Keep in mind that if you have been explicitly linking to -lgfortran using -L%p/lib/gcc44/lib this will have to be changed to -L%p/lib/gcc4.4/lib/i386. Likewise, if you are on i386 fink and want to generate 64-bit code you will pass -m64 and use -L%p/lib/gcc4.4/lib/x86_64 if you are explicitly linking. Jack -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
