Re: [Fink-devel] gcc4x/gcc4x-compiler packages
Daniel, Why do you say that 'info /sw/share/info/gcc-fsf-4.5' is need? With my currently proposed packaging a simple 'info gcc-fsf-4.5' is sufficient to find the renamed info file in /sw/share/info with or without the main gcc45 symlink package installed. Jack -- ___ 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] %N-shlibs (= %v-%r)
One piece of legacy coding left in the gcc4x packages which perplexes me is the use of... %N-shlibs (= %v-%r) instead of... %N-shlibs (= %v-%r) for the Depends field of the main gcc4x package. Was there a bug in fink at some point that required the use of = rather than =? I was going to change that as well but wanted to make certain there wasn't some obscure reason for that particular conditional. Jack -- ___ 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] %N-shlibs (= %v-%r)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/28/10 9:22 AM, Jack Howarth wrote: One piece of legacy coding left in the gcc4x packages which perplexes me is the use of... %N-shlibs (= %v-%r) instead of... %N-shlibs (= %v-%r) for the Depends field of the main gcc4x package. Was there a bug in fink at some point that required the use of = rather than =? I was going to change that as well but wanted to make certain there wasn't some obscure reason for that particular conditional. Jack Convenience, possibly. The bug hasn't gone away. If the main package has Depends: %N-shlibs (= %v-%r), if a user has the main and -shlibs installed they can't update to a new version-revision in one step. The build will be performed, but fink won't install the update: the new -shlibs has to go in first, and the old main package will complain because of the %v-%r mismatch. But afterwards apt-get is perfectly happy to figure out how to do the upgrade. I'd argue that (= %v-%r) is a safer option. - -- Alexander Hansen Fink User Liaison -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvYO6IACgkQB8UpO3rKjQ+lugCeKNYewd0UnNr9HOHR2sULhJ43 46oAoI90OLjP13LEPT7gHH26ENmUFZG9 =n0GD -END PGP SIGNATURE- -- ___ 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] mach-o lto progress
FYI, for those interested, good progress is being made towards adding Mach-O LTO support for FSF gcc. Like the recently committed patches to add COFF LTO support, these changes should land in gcc 4.5.1 before release (knock on wood). The current progress is documented here... http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43729#c12 I don't plan on holding the gcc45 package up for this but will likely put a gcc45 snapshot package on fink tracking as soon as these changes arrive in gcc-4_5-branch so folks can test and file LTO bug reports. Nice. Jack -- ___ 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] gcc4x/gcc4x-compiler packages
On Wed, Apr 28, 2010 at 09:15:18AM -0400, Jack Howarth wrote: Daniel, Why do you say that 'info /sw/share/info/gcc-fsf-4.5' is need? With my currently proposed packaging a simple 'info gcc-fsf-4.5' is sufficient to find the renamed info file in /sw/share/info with or without the main gcc45 symlink package installed. As mentioned several email ago, xrefs from one .info to another. For example, in the gcj info page in the Invoking gcj node is a link to the Option Summary node of the gcc info page. You have gcj at gcj-fsf-4.5 and gcc at gcc-fsf-4.5. If I don't have gcc4.5 installed, then I only have gcc-fsf-4.5 (not gcc) and the link is broken. If I have gcc4.4 (or any other than 4.5 gcc) installed, then the link goes to *that* gcc, not the 4.5 one (i.e., gcj-fsf-4.5 is sending me to a symlink to gcc-fsf-4.4 rather than gcc-fsf-4.5). That's the problem I'm trying to solve. If the documentation isn't self-consistent (from the perspective of the reader), it's not useful/usable. dan -- Daniel Macks dma...@netspace.org http://www.netspace.org/~dmacks -- ___ 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] %N-shlibs (= %v-%r)
On Wed, Apr 28, 2010 at 09:44:02AM -0400, Alexander Hansen wrote: On 4/28/10 9:22 AM, Jack Howarth wrote: One piece of legacy coding left in the gcc4x packages which perplexes me is the use of... %N-shlibs (= %v-%r) instead of... %N-shlibs (= %v-%r) for the Depends field of the main gcc4x package. Was there a bug in fink at some point that required the use of = rather than =? I was going to change that as well but wanted to make certain there wasn't some obscure reason for that particular conditional. Jack Convenience, possibly. The bug hasn't gone away. If the main package has Depends: %N-shlibs (= %v-%r), if a user has the main and -shlibs installed they can't update to a new version-revision in one step. The build will be performed, but fink won't install the update: the new -shlibs has to go in first, and the old main package will complain because of the %v-%r mismatch. But afterwards apt-get is perfectly happy to figure out how to do the upgrade. I'd argue that (= %v-%r) is a safer option. I think fink's SysState fixed that bug. If you have installed the pair with %N:Depends:%N-shlibs(=%v-%r) and you fink update %N-shlibs to a newer version or revision, fink should recognize that 1) this will break the dependency of the installed %N, and 2) that simultaneously updating %N will solve he problem, and so do it that way. It may not be able to handle looking more deeply into the dep tree and it might not work if %N and %N-shlibs are not in the same .info file (two splitoffs, or one splitoff of another)...can't remember how robust the thing is. For libraries, the = actually prevents breakage of symlinks. For example, foo1-dev has libfoo.dylib-libfoo.1.0.1.dylib, with libfoo.1.dylib (the install_name) and libfoo.1.0.1.dylib in foo1-shlibs. Now comes a new package version (same install_name) that has libfoo.1.0.2.dylib istead of libfoo.1.0.1.dylib. Just updating the -shlibs package (allowed by a = dependency) breaks the libfoo.dylib symlink, which also breaks building of any package that BuildDepends:foo1. Using = means they stay in sync. Using = also means the .h and other compile-time files and tools are perfectly (self-consistent set) matched to the .dylib. I don't know what happens if gcc (the front-end programs) from one %v of a gcc suite are used with the libraries (-shlibs package) from a different one. No idea if there are symlinks and other pointers that break (recent libtool2 uses libfoo.dylib-libfoo.1.dylib not -.1.0.whatever). dan -- Daniel Macks dma...@netspace.org http://www.netspace.org/~dmacks -- ___ 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] Packaging software from upstream VCS
Hi, I want to package htop software that is currently unavailable in fink. Unfortunately original htop from sourceforge supports only linux however there is a htop-osx project at github (http://github.com/AndyA/htop-osx) that looks like a htop fork that works on osx. This fork contains no tarballs, so clone/checkout from VCS is the only way to get sources. So what is a correct way to package such software? I've created tarball myself and placed it to directory with other fink downloads. After playing a bit with auto* I was able to build it and get .deb. Also should I contribute htop package to fink? -- WBR, Dmitry signature.asc Description: Digital signature -- ___ 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] Packaging software from upstream VCS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/28/10 6:18 PM, Dmitry Nezhevenko wrote: Hi, I want to package htop software that is currently unavailable in fink. Unfortunately original htop from sourceforge supports only linux however there is a htop-osx project at github (http://github.com/AndyA/htop-osx) that looks like a htop fork that works on osx. This fork contains no tarballs, so clone/checkout from VCS is the only way to get sources. So what is a correct way to package such software? I've created tarball myself and placed it to directory with other fink downloads. After playing a bit with auto* I was able to build it and get .deb. Also should I contribute htop package to fink? If you'd like to contribute it to Fink, we'd want 1) The tarball to be placed somewhere online. 2) It needs to have a version associated with the vcs revision number attached to it. - -- Alexander Hansen Fink User Liaison -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvYvu4ACgkQB8UpO3rKjQ/Z8gCdElmRNyaTceaVlVHo68ob+2Mi Zq4AoJKJIPDIUuAncoDZ4TTI+etZIy+Q =5+i7 -END PGP SIGNATURE- -- ___ 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] Packaging software from upstream VCS
On Apr 28, 2010, at 7:04 PM, Alexander Hansen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/28/10 6:18 PM, Dmitry Nezhevenko wrote: Hi, I want to package htop software that is currently unavailable in fink. Unfortunately original htop from sourceforge supports only linux however there is a htop-osx project at github (http://github.com/AndyA/htop-osx) that looks like a htop fork that works on osx. This fork contains no tarballs, so clone/checkout from VCS is the only way to get sources. So what is a correct way to package such software? I've created tarball myself and placed it to directory with other fink downloads. After playing a bit with auto* I was able to build it and get .deb. Also should I contribute htop package to fink? If you'd like to contribute it to Fink, we'd want 1) The tarball to be placed somewhere online. 2) It needs to have a version associated with the vcs revision number attached to it. github can also generate tarballs of specific revisions on the fly. For example, the tarball of the most recent commit would be http://download.github.com/AndyA-htop-osx-34864f0.tar.gz. That's a neat feature of github. Daniel -- ___ 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
