Re: [Fink-devel] texinfo should be a standard package?

At 9:22 Uhr +0800 01.02.2002, Andrew Rohl wrote: >Have souped up my old 7300 so it can run OS X and fink. installed >bash as my first package and tried to do info bash - no info. So >all packages that contain info files should depend on texinfo but >perhaps we make texinfo part of the initial

Re: [Fink-devel] blackbox mirror: portal.alug.org AWOL?

Thanks for the reminder. I'll take care of it. -christian On Thursday, January 31, 2002, at 10:02 PM, Ben Gertzfield wrote: > Trying to install blackbox from fink unstable with 'sudo fink install > blackbox' for the past few days has only gotten me: > > curl -L -O > ftp://portal.alug.org/pub/bl

[Fink-devel] cvs trouble

I can't do "cvs commit" in the directory ../unstable/main/finkinfo/net . I keep getting a message cvs server: [04:13:32] waiting for anoncvs_fink's lock in /cvsroot/fink/packages/dists/unstable/main/finkinfo/net Anybody know how to kick the cvs server? -- Dave __

[Fink-devel] langinfo.h

I've updated gnumeric so that it doesn't run into trouble if the user has /usr/include/langinfo.h installed. gnumeric's configure script checks for langinfo.h, which is normally not present on a darwin/OS X system. However, apparently Gnu-Darwin installs this header, and that was confusing the g

Re: [Fink-devel] texinfo should be a standard package?

At 19:48 Uhr +0800 01.02.2002, Andrew Rohl wrote: >Max > >>texinfo certainly is not an essential package and hence shouldn't >>be in the base install. > >thanks for the swift response! I guess it depends on the definition >of essential! If its required by say 50% of packages, would it be >ess

[Fink-devel] Re: pygtk

On Thu, 31 Jan 2002 11:52:27 -0600, Doug Rowland wrote: > I was trying to install the pygtk package on OS X 10.1.2 on an HFS > filesystem and there is a problem with the case-insensitivity. In > particular, there are two files GTK.py and gtk.py which are distinct but > HFS overwrites gtk.py wit

Re: [Fink-devel] cvs trouble

I have reported this to sourceforge as a support request (to remove a stale lock file), which seems to be the correct thing to do. Hopefully we will regain access to the net directory in a day or two. -- Dave > I can't do "cvs commit" in the directory ../unstable/main/finkinfo/net . > I keep

Re: [Fink-devel] cvs trouble

At 16:17 Uhr -0500 01.02.2002, David R. Morrison wrote: >I have reported this to sourceforge as a support request (to remove a stale >lock file), which seems to be the correct thing to do. Hopefully we will >regain access to the net directory in a day or two. > > -- Dave > > >> I can't do "cvs

[Fink-devel] Help porting

I'm in the midst of porting subversion to OS X, creating a Fink package in the process. Subversion's source tree is a rather complex beast that includes a number of other packages directly within and, hence, has a number of different beasts that use various forms of autoconf. It appears that

Re: [Fink-devel] Help porting

The question is, what libtool version are they using? I have setup subversion in the past succesfully, but that was one or two milestones ago I believe. Max -- --- Max Horn Software Developer email: phone: (+49) 6151-4948

Re: [Fink-devel] shlibs (was: libpng)

On Thursday, January 31, 2002, at 11:28 AM, Max Horn wrote: > Achieving that is a quite involved task indeed, since it means you have > to keep parts of a package around (like libtiff.3.dylib), enve though > the rest of the package is removed, creating "orphaned" files that > nobody owns anymo

Re: [Fink-devel] shlibs (was: libpng)

At 17:31 Uhr -0600 01.02.2002, Ken Williams wrote: >On Thursday, January 31, 2002, at 11:28 AM, Max Horn wrote: >>Achieving that is a quite involved task indeed, since it means you >>have to keep parts of a package around (like libtiff.3.dylib), enve >>though the rest of the package is removed,

Re: [Fink-devel] shlibs (was: libpng)

I've been studying the Debian policy about shared libraries, and I think I understand their strategy much better now. It has several components. First, the libraries themselves are separated from the headers -- you have to have two packages per program. (Well, actually three in many cases, beca

Re: [Fink-devel] shlibs (was: libpng)

That sums it up pretty well, indeed. The only potentially trouble spot is that the order in which (in your example) db3 and db4 are installed affects to which the db.dylib symlink points. If a package has to link against a particular version, that could generate problems. Alas, in such cases,

Re: [Fink-devel] shlibs (was: libpng)

Yes, the installation order business bothered me. One possibility is to force people to install in the correct order, by this trick: Package: db1 *** Package: db2 Replaces: db1 *** Package: db3 Replaces: db1, db2 *** This way, if you try to install db2 after db3, you will be told that you

Re: [Fink-devel] shlibs (was: libpng)

On Friday, February 1, 2002, at 07:19 , Max Horn wrote: > That sums it up pretty well, indeed. > > The only potentially trouble spot is that the order in which (in your > example) db3 and db4 are installed affects to which the db.dylib > symlink points. If a package has to link against a partic

Re: [Fink-devel] Help porting

Did you build the client or the server? The client is trivial; pretty much builds out of the box. The server is more problematic in that it requires the mod_dav.h header, db4, and apr-- apache portable runtime. mod_dav.h is interesting in that it can only be had by installing mod_dav. Ap