Posted by Simas |

Posted by Simas |

Posted by Simas |

This entry is somewhat hard to write. Maybe I just don't know how to start this post :)

Ok, let's start. There are three basic ways to find out, what are dependencies of given port:

• make -V RUN_DEPENDS -V BUILD_DEPENDS
• make all-depends-list
• look at Makefile

Well, this is not what I want. Usually after using one of the above (third option, mostly ;) ), you run pkg_info just to find out, what ports are present and what are missing. And it takes some time for such a simple task. So, I wrote simple addition to Makefile to give some more information on ports. It adds two more targets - "show-rdeps" for run depends and "show-bdeps" for build depends. I haven't made up my mind how to call these - "bdeplist" and "rdeplist" seems to be more correct when looking to other already present targets, but somehow show- prefix is more intuitive to me.

sysutils/portupgrade$ make show-rdeps
[+]  ruby-1.8.2_1
[+]  ruby18-bdb1-0.2.2

[+] indicates installed port, and [-] port, which is not present on the system (of course :)). What you need to do is fetch this and place it to /usr/

Of course, it could be done better (for example, checking for real dependent file's presence on the system), but I think this is overkill, as is recursive checking for dependencies in this case. This makefile gives enough information, at least for me.

What I'm still missing on ports, is a nice way on figuring out what options for given port are. It would be easy to implement, if makefiles had some line like this:

VARIANTS= NO_GUI USE_PYTHON SHOOT_AT_SIGHT

I couldn't think of any occasions when this would break something, and it doesn't add any real maintenance overhead. Oh, well, maybe it's not important for most people out there.

Posted by Simas |

I don't know, how to feel about this. It appears FreeBSD is #11 linux distro. Ummm...

"FreeBSD is to all intents and purposes is a Linux and Unix mixture".

Yup, as I said, very solid.

Posted by Simas |

Ummm... At first I thought to write very long and clever entry, but I guess I'm just lazy today. So, instead I'll say this - it sucks. Well, at least on Mac. I can get japanese, korean and hell knows what else working, but not lithuanian.

First of all, the main reason for me to switch from vim to emacs is wiki. I want to have my own personal wiki, but I don't want some shitty XXXwiki running on apache on my notebook, why should I? PersonalWiki is too amateurish. VIM wiki mode is too incomplete. There was some app written in ruby, which suited my needs, but I forgot to bookmark it in del.icio.us, and now I can't remember what it was (and even google doesn't help). Emacs has muse-mode, which is nice. It's the thing. Well, except that emacs... You know. Sucks. Or maybe it's that I suck. Either way, I can't get emacs working with utf-8 and lithuanian keyboard on mac. Oh, fuck it, I won't waste your time explaining all these stupidities I ran into.

P.S. This entry is a note to myself, just in case I'll try something like this again someday..

P.P.S. It's funny, the old habits doesn't go away easily. I can't count how many times I ended up editing ~/.emacs with vim..

Posted by Simas |

Posted by Simas |