Interview with Fink's Project Leader 30
Gentu writes "There is a interesting interview over at OSNews with Fink's project leader, Max Horn. They discuss Fink's relationship with Apple, integration of their Unix/Linux ports to Mac OS X via Debian's packaging solution, ease of use on installation of the .deb packages, AltiVec optimizations and more."
Re:Fink is a problem (Score:2, Informative)
Re:Fink is a problem (Score:3, Interesting)
And why on earth do you say that the Fink-developers wouldn't like Apple? Think about it - by making all those applications available to the Mac OS X users they're actually helping Apple. What about Apple's X11 port? Users running X11 on Mac OS X heavily rely on Fink for their software.
Why should the Fink-developers run PCs instead of Macs? Why s
Re:Fink is a problem (Score:1)
1. Offer a true package manager like the one on NeXT that they are using, sans all of its useful features.
2. X11 from day one. This may be the one thing that would have made MacOS X 1.0 useable AND would have convinced more traditional workstation users that Apple is serious about open environments. The official X11 f
Re:Fink is a problem - Apple is a problem (Score:1)
YES, it is a dated joke but "raping a dead horse?" This will require a recount from the judges.
Here goes:
"Gore never said he invented the Internet.
Re:Fink is a problem (Score:5, Insightful)
"They can't seem to get that NIH attitude out of their heads even when they go open source."
You mean like USB, Ultra ATA, and Gigabit Ethernet? Yeah! Apple needs to be more standards compliant damn it and support... oh, they *do* support them and have for quite some time.
Or do you mean things like gcc3.1, gprof, XFree86, libtool, automake, KHTML, &c?
"Fink and GNU/Darwin are clean up efforts in reponse to Apple's failure to:"
You do realize that it isn't Apple's responsability to do everything for you?
Boo hoo! it didn't ship with TeTeX, how am I ever supposed to do my document typesetting! They must not be serious about the Unix community or they would include such essentials that of course 90+% of their userbase--both users and developers--is going to use.
" X11 from day one. "
I don't suppose that you have heard of the XonX project?
"useable AND would have convinced more traditional workstation users that Apple is serious about open environments."
This statement does not grok. Most "tradiational workstation users" don't give a damn whether Apple is "serious about open environments."
"The official X11 for OS X package remains in beta to this day."
Considering it was released in January and we are on Beta 3 right now, which is more than useable. It took Mozilla how long to get through its own Beta stage?
"Fully embrace a mainstream open source OS. "
'They have done so much that no-one else in the field ever has... but damn them! They aren't doing enough!'
Am I getting the gist of your argument?
You do realize that, for the vast majority of us, we try to use what works best for us and do not choose our platform soley on the basis of religious zeal.
" I don't care how black-turtle-kneck-sweater cool the MACH kernel is"
The variant of mach they are using is almost, but not quite, entirely unlike mach. It has been so heavily revised it isn't even funny.
"If they aren't ready with a mechanism for weekly or daily patches,"
You mean like CVS?
Incidentally, so Apple left something for groups to do--such as produce fink--what is your point?
Also, am I the only one who doesn't install the newest library just because its available? Seriously, you do realize I have software that I need to have work?
Re:Fink is a problem (Score:5, Interesting)
No need, I am dealing with a bug in Apple's gcc3.1 as we speak.
In response I use Apple's gcc for things where the bugs do not exist and gcc3.3 (compiled from cvs) for times when they do. A good craftsman never blames his tools, but always tries to make sure that his tools are up to his own specification.
Apple did introduce a few bugs, they also removed a few. It's the way it goes.
"Where on the Jaguar disc can I find XFee86?""
What you are doing here is called "not reading what I wrote".
"I can safely say they ARE trying to do everything for me and let's try an analogy:"
Not at all. Not all of their machines ship with AppleWorks, for instance (mine didn't), QuickBooks is not in-house by any means, and they are (or at least were) offering a steeply discounted version of Microsoft Office.
They are not trying to do a lot of things for me. I have to purchase Keynote separately, download TeTeX on my own, &c. Considering how small of a percentage of users ever write anything in LaTeX or see LaTeX code...
"Why can't Apple's out-of-the-box Unix be as compelling to RedHat users as say, their Final Cut Pro is to Avid users?"
This would be called a "false analogy".
"I don't want to get into 'my Apple loyalty is bigger than yours' but it is my 13-year admiration of their complete product line"
I've been using macs since 1984 and have owned or had as family computers over 10 macs (Original, Plus, SE, LC, Centris 650, 7100, G3MT, iMac, iBook, and a 12" PowerBook). I used to subscribe to the MacMarines mailing list and was (and still am) a Mac Evangelist.
I also have done a lot of work with Linux and ran my systems in dual boot (with LinuxPPC or MkLinux, depending on the system) until the release of MacOS X 10.1.
Yes, I also ran MacOS X 10.0 and even the MacOS X 10.0 Public Beta.
"ot shipping with a working package manager "
Is it annoying? Sure. Can it be worked around? Easily and through commonly available (and easily installable) means. Therefore I do not complain.
"explain how I perform the equivalent of 'rpm -e apache' on a freshly-installed Mac OS X box?"
1) Apache comes preinstalled.
2) Try fink.sourceforge.net
3) Once again, this is called "not reading what I wrote"
"Kudos to Fink and and GNU/Darwin to finding workarounds to this situation."
I don't consider it "a workaround," I consider it "adding useful functionality to a system."
There is a *big* difference between those two.
". I simply don't understand why it is a problem in the first place."
Neither do I (though I have a few guesses involving Apple's tech support getting swamped with phone calls from people trying to install Unix software and thinking that Apple supported it since they were using an Apple utility), however, considering we are on 10.2, and are about to go to 10.3, Apple mentions Fink on their website, and now Apple has a publically available X11 implementation, why are you still up in arms?
"That was on Mac OS X 1.0 install disc 3?"
Once again, "not reading what I wrote."
I don't care whether it was on the 10.0 install disc. I doubt I could *find* my copy of the 10.0 install disc if I went looking for it.
Also, when it is readily available via the internet or through CDs, why is it a problem if it doesn't ship with it? Oh boo hoo, it takes that much longer to get working?
"These guys seem to: www.macdevcenter.com Do you put O'Reilly and Associates in the same Trolling Idiot category as you put me?"
I'm going to venture a guess that they would be chugging along just fine if XonX were the only implementation of XFree86 involved on the Mac and we all were using OrobusOSX.
They are also not "traditional workstation users" by any stretch of the imagination, which is what you claimed. Nor do they seem to be whining, like what yo
Re:Fink is a problem (Score:1, Troll)
"Congratulations, you just demonstrated a complete and total lack of knowledge of how the proprietary software cycle works."
Indeed, I naively assumed that Apple's Open Source OS initiative would deliver a few system administration tools (such as a full-featured package manager) that I had taken for granted under RedHat Linux. Ha ha on me. Moving on, thank you Fink for filling the gap. I admire your endurance as an Apple apologetic. I lost that zeal years ago.
Peace.
Re:Fink is a problem (Score:5, Insightful)
It's true that Mac OS X is probably the only modern Unix variant that doesn't ship with X11 by default (yet), but has it ever occurred to you that the reason for that may be that Mac OS X already has a different window manager on board (while for the others it's either XWindows or nothing) which is much more important to most Mac users? I really don't understand why you are so obsessed with X11 not being included by default.
Those "mainstream open source OS"'s lacked several key features Apple needed in its OS at the time Mac OS X development started and they are only now catching up. Which features? For example proper smp support (multi-processor Macs finally had to be able to their fullest potential), proper real-time support (Final Cut Pro anyone?) and low latency support (low-level audio, user interface).I really don't understand why you think Apple should do everything based on open source. What is the problem with using existing stuff of which you think it's done well, and do other things (of which you think you can do them better) yourself? What is the problem with first focussing on your largest user base (Mac users) and only when you're confident you're on the right track there, starting to spend resources on other target groups?
I'm not trying to be elitist here, I'm just trying to point out that Apple is a company with a small market share and thus it can't take very large gambles (it doesn't control the market). You call opening the Darwin source (and several other packages) a leap of faith, but there's no large risk involved there. At worst, it has cost them a bit extra in terms of bandwidth and HD space. On the other hand, it gave/gives them extra publicity, it makes it much easier for driver developers and they get some free bug fixing in the process. On top of that, the open source world also benefits from it, so it's a win-win (or WIN-win for Apple according to a lot of people, but even then everyone still gains) situation.
Re:Fink is a problem (Score:2, Interesting)
I perceived a desire (personal and in others) for (1) a native package manager in OS X (just as existed long ago in NeXTStep) and (2) and X11 package... just as existed for NeXTStep long ago (granted, not out of the box).
How do you guys keep interpreting this as a request for "a lot more programs?" Am I going out on a limb to suggest that the loss or th
Re:Fink is a problem (Score:2)
I got that impression from the following part of your original mail:
I thoug
Re:Fink is a problem (Score:5, Insightful)
Instead of trying to create software that piggybacks on GNU/OS X why aren't they working on GNU/Darwin?
You're missing the whole purpose of Fink. It's a porting project. Of course there's coding work involved, but the idea is to get software that runs on other unices to work on OS X / Apple Darwin.
Re:Fink is a problem (Score:4, Insightful)
Maybe because there isn't such a thing as GNU/OS X?
Less flippantly (but only slightly): Maybe because the purpose of fink is to improve the ease of UNIX integration with Apple's MacOS X?
"It seems to me that they don't like apple very much for some reason."
You must not have read the same article I did.
The one that said:
<<Overall, the mood at Apple seems to be friendly towards Fink, they refer to us in various places of their homepage, for example.>>
" Political reasons maybe?"
No, it would be for "political reasons" if they suddenly started working working exclusively on the GNU-Darwin project.
"Maybe they should have bought PCs instead of a MAC and run linux."
You do realize that it isn't an acronym? Mac, short for Macintosh.
You also realize that most of us use OSX because we happen to like OSX and because it works for us? *Not* for solely political reasons?
Re:Fink is a problem (Score:2, Funny)
GNU/DARWIN like drinking from a spittoon. (Score:4, Interesting)
Here's my own opinion on what distingusihed gnu darwin from fink. While Gnu/darwin portrays it self as a GNU extension for OSX it really wants to mostly replace the core functions of the command line interface. FOr example, when you install it it overwrites make, tar and other key programs with its own versions. These can be fixed by fiddling with links and such but its a nightmare when all of a sudden your make files (like all of fink) break.
in contrast fink, in the apple manner, installs it self in its own files system where it can easilty be separate from the apple core system. It uses the apple tools and when it cant installs its own in its own filesystem not in /bin. Its easy to unistall or re-install. it may get broken by a apple upgrade but it wont break the OS. Gnu/darwin can break the OS since it write to /bin and /etc.
Finally installing gnu/darwin was like drinking from a spittoon, to install just a tiny bit you had to take a big slug of things you did not expect to get sprayed all over your /bin directory. Fink comes in fairly small chunks.
my own feeling from reading he gnu/darwin web pages is that it was a stalking horse to completely replace the OS.
the problem I had was that at first most of the major scientific apps were ported to gnudarwin and not to fink. indeed this is still true. But each month I see more of these apps joining fink.
basically gnu darwin exemplifies everything I hate about linux and its too complicated way of installing and managing packages. Fink is a nice clean break and done right.
Fink is nice (Score:3, Informative)
Screenshot! (Score:4, Informative)
Re:Screenshot! (Score:2)
Re:Screenshot! (Score:2, Informative)
Re:Screenshot! (Score:1)
Re:Screenshot! (Score:1)