Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Learn how to build, compile, and customize mutt' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Learn how to build, compile, and customize mutt
Authored by: vdanen on Mar 06, '07 01:28:48PM

I chose /sw because there's where I put all my compiled stuff. I'm not strictly "bypassing" fink... but fink doesn't always have the latest mutt nor does it compile with the sidebar patch. AFAIK, fink doesn't have lbdb either. As for fink not knowing mutt is there, it doesn't matter. There's nothing that actually *requires* mutt, so fink not knowing about mutt living in /sw is ok.

As for muttng, it's a nice idea, but nothing has been checked into svn in 8 months or more, which means muttng is not the latest version of (mainstream) mutt anymore. It might have some of this stuff in there already, but it's not the latest version (with it's associated feature enhancements and bugfixes).

Finally, you could put stuff in /usr/local/bin, but for me, /sw just made more sense. It's just a matter of changing --prefix in the stuff you're compiling (but since the other stuff like newer fetchmail/procmail/etc. live in /sw, it keeps it all consistent for me).

[ Reply to This | # ]
dead horse
Authored by: SeanAhern on Mar 06, '07 02:15:28PM

I hate to be a bother, but I am just very curious to know why "/sw just made more sense". I can't think of a single reason why that would be, and can only think of downsides. Not to beat a dead horse, but you've really made me curious now what the reasons are that cause it to make "more sense".

[ Reply to This | # ]
dead horse
Authored by: vdanen on Mar 07, '07 09:12:03AM

Hmmm... well, for me, /sw works better than /usr/local. In /usr/local, I can stick stuff specific to the machine (which is traditional what /usr/local is for, hence the "local" part). But with /sw I can manage fink on one system and then copy the entire /sw tree to other machines (which keeps all my tools, etc. in sync). Instead of copying two trees (/sw and /usr/local) to other machines, I just have to copy one. Since it really doesn't matter to fink that mutt and friends are living there, it doesn't hurt fink. If I ever want to remove it, I don't run an uninstaller for fink, I would just "rm -rf /sw". Since a lot of my mutt setup relies on things in /sw, if I ever were to remove fink, stuff in mutt just wouldn't work (or work as nice). So keeping it all in one place, again, makes sense to me.

Now, nowhere in the article do I say you *have* to put it in /sw. You're compiling it, so you're obviously free to point --prefix to wherever you want. If /usr/local works better for you, go to town and install things there. Since this was a write up of my full mutt setup, instead of going through and changing the paths I use, which I could have done I suppose, I just put what I do verbatim, and I use /sw. That doesn't mean *you* have to. =) It's just what I do, because it makes sense to me and with how I replicate my setup between my macpro and my macbook pro. Obviously if you want things differently, or disagree with my installing to /sw (a pristine fink means nothing to me, largely because it means nothing to fink). If someone felt like it, they could create /mutt and use --prefix=/mutt for everything too and it would still work.

[ Reply to This | # ]
Authored by: SeanAhern on Mar 08, '07 04:08:54AM

Thanks for your explanation. Of course, you can install any tool into any location -- I've done it for years.

Understanding that you consider /sw to be the "local machine customization" location that allows you to stay separate from the rest of the OS was the missing bit. I can see keeping things in one location making it easier to move software installs from one machine to another. I personally wouldn't choose /sw, but I understand your thought process now.

Thanks for taking the time.

[ Reply to This | # ]
Authored by: vdanen on Mar 08, '07 09:18:38PM

No problem. Yeah, I do things a bit backwards on my macs... =) On my Annvix boxes, it's always "my stuff" in /usr/local, but I don't do that here as I find too many other external/third-party packages put stuff in /usr/local so I prefer using /sw for my own stuff (since, in a sense, I'm compiling the fink stuff myself I guess).

Yes, I'm a little odd, but the "system" makes sense to me.

[ Reply to This | # ]