Looks like I got myself into trouble again.

After I accepted a hat from portmgr, I started looking at pkg_install again. I’ve already done some cleaning which I mentioned previously but it now seems like i have a new part-time job.

I’m working on a config file support right now. I’ve done some more cleaning up (removing FreeBSD 5.x support, fixing pkg_info ftp://...). I’ll have a look at PRs later.

Code is living at http://git.xbsd.org/projects/pkg-install/. To check it out:

$ git clone git://git.xbsd.org/projects/pkg-install.git
$ cd pkg-install
$ git fetch origin cleanup:cleanup (if you want the cleanup branch)
$ git fetch origin config:config (if you want the config branch)

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

I figured I could give a small update on what I’m doing these days.

If you’re reading Planet FreeBSD, you already know that I’ve been offered to join portmgr@ a few days ago. Since then I’ve done some cleanup in pkg_install related stuff: removed pkg_sign, sync’ed RELENG_7 and RELENG_6 with HEAD, removed old pkg_install-devel port, updated pkg_install port, added a distfile target to pkg_install in src/ to generate a new distfile for use with ports/, ...).

I was also browsing pkg_install code to look for ancient/unsupported/broken code. I’ve found that “@option extract-in-place” wasn’t used anywhere under ports/. If you’re too lazy to read pkg_create(1), basically it extracts the contents of a package straight into $PREFIX rather than to a staging area first. Pav ran an exp-build to see if defaulting to in-place extraction breaks anything and, obviously, it did. Thankfully I could reproduce quickly and I’ll investigate in the next few hours. I expect to find loads of gems like this one.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.