mobi2mobi install problems on mac

[ATDrake]

The .profile PATH reset is automatically taken care of by the initial MacPorts installer.

But I override it because I only use MacPorts for one thing*, so I don't need it handling any of my other Unix stuff which I prefer to install and manage myself.

Anyway, while reinstalling all the Mobi2Mobi supporting packages to go with the new default version can be tedious, they probably only have to do it once.

Or until their Perl gets updated and breaks the library links, which is what happened on my other computer which doesn't have MacPorts installed.

* I gave up on installing the devel versions of Wine manually as too much hassle, considering how often it got updated.

[pilotbob]

Originally Posted by ATDrake

But I override it because I only use MacPorts for one thing*, so I don't need it handling any of my other Unix stuff which I prefer to install and manage myself.

Why? there are ports for pretty much anything you want to install.

You can install GD2 without using MacPorts.. but it isn't easy or fun.

BOb

[ATDrake]

Really? I had no problems installing the GD-related stuff at all, on either of my machines (10.4 PPC & 10.6 Intel). Glib, on the other hand, I had to tweak very slightly.

Sometimes I like to try out middling obscure stuff that doesn't make it to MacPorts. Like Checkmate mpck which checks your mp3s for file errors, which is listed on Freshmeat (and works quite nicely, by the way), but is not the sort of thing that anyone bothers to port.

Or jpegoptim, which I find quite useful for reducing filesizes losslessly, but which I guess the official jpeg libs being up to v7 or v8 and including that feature makes kind of moot.

I guess I've just gotten into a DIY habit when it comes to doing "./configure; make; sudo make install" with promising-looking stuff directly from the developer's site, rather than firing up MacPorts to see if there's a port.

I'm lazy and the former just seems easier somehow.

[pilotbob]

Originally Posted by ATDrake

I guess I've just gotten into a DIY habit when it comes to doing "./configure; make; sudo make install" with promising-looking stuff directly from the developer's site, rather than firing up MacPorts to see if there's a port.

I'm lazy and the former just seems easier somehow.

Hmm.. I just search on the macports site...

TO each his own. I was just trying to create a guide that would make it easy for non-techie folk to be able to use mobi2mobi on their mac. That's why I wrote the guide in the first place.

BOb

[ATDrake]

Originally Posted by pilotbob

Hmm.. I just search on the macports site...

But… that's a whole extra site visit. And additional typing, too!

But seriously, the Visual Install guide is indeed very handy and I did use it to help get set up the first time* around. I'm sure it would have been much harder to do so without the useful pointers to the various prerequisites.

Thanks for putting it up.

* Although for a completely fresh system install after I had this B-tree corruption issue, I had to track down a few more dependencies by hand than were mentioned in the guide; unfortunately I can no longer remember which.

[pilotbob]

Originally Posted by ATDrake

But… that's a whole extra site visit. And additional typing, too!

But seriously, the Visual Install guide is indeed very handy and I did use it to help get set up the first time* around. I'm sure it would have been much harder to do so without the useful pointers to the various prerequisites.

Thanks for putting it up.

* Although for a completely fresh system install after I had this B-tree corruption issue, I had to track down a few more dependencies by hand than were mentioned in the guide; unfortunately I can no longer remember which.

Anyone feel free to update the guide as needed... That's the whole point of it being on the Wiki.

BOb