Some time ago, there was an application called pkgmanager, available in pkgsrc-wip. It worked by tracking ‘wanted’ packages in pkgsrc, and upgrading based on that list. It hasn’t been updated in some time, however, and may not even build.
‘Rumko’ has written a replacement, called rpkgmanager. The Gitorious page linked in the previous sentence includes the URL to download the code via Git, so it’s available to try now even though it’s not yet in pkgsrc.
You know what we could use for pkgsrc, and all the other port/package collections? Explanation. They face the same problem phoneapplicationstores face: too many programs to easily select what you need. You could certainly build a whole site just around package reviews; it’s even possible to argue that Ubuntu or PC-BSD are built around just making some 3rd-party-app choices ahead of time on an existing operating system. Anyway, here’s an article talking about that idea specifically around the Apple App Store. Please won’t somebody who is not me do something like that for pkgsrc?
As I found out directly, upgrading from pkgsrc version 2010Q1 to 2010Q2 has a minor quirk: binary packages for 2010Q2 will refuse to install with an older version of pkg_install. Rebuild pkgtools/pkg_install to the 2010Q2 version and the problem will go away.
happened to notice that recent libkinfo changes broke sysutils/estd. It’s fixed by rebuilding the program, though this may affect a few other packages. This only affects people running bleeding-edge DragonFly 2.7.
If you are running DragonFly 2.7, Matthew Dillon has made some kernel changes, so updating your 2.7 machine will require a full buildworld cycle, not quickworld.
The binary packages for 2.6 and 2.7 have been updated to pkgsrc-2010Q2. This means that pkg_radd will automatically pull down newer packages, and you should make sure your /usr/pkgsrc is using the pkgsrc-2010Q2 release if you want to be sure there’s no version mismatches.
On email@example.com, Greg Troxel proposed getting rid of gimp-print and associated packages. It’s been superseded by gutenprint-lib, so it may be worth switching now for the newer printer drivers, even if the package isn’t eliminated.
There’s an online hackathon (the 14th!) planned for July 30th through August 2nd for pkgsrc (and probably some NetBSD material too) at FreeNode/#netbsd-code on IRC. Aleksej Saushev’s post has more details. At least it’s cheap to attend!
Matthew Dillon set up a git copy of the pkgsrc repository some time ago. However, it’s had syncing problems, and there’s an ‘official’ pkgsrc git repository now which does not have the problems. You can still pull from the same place, but it’s the ‘master’ branch now. His heads-up message describes how to switch.
If you’re following bleeding-edge pkgsrc, there’s been an update to png. Since a lot of programs depend on it, a lot of programs will need to be rebuilt. Be ready for it. This won’t affect anyone using quarterly releases.
Another article talks about inspecting network traffic using various tools including tcpdump and wireshark. It is a tremendous advantage to see what happens on a network at the most basic level, so this is a good skill to pick up.
Thomas Klausner has a writeup of some project ideas or goals taken from the recent pkgsrcCon. A followup has me thinking: if the -uu option updates dependent packages with pkg_add, does that mean ‘pkg_radd -uu packagename” will do all updating possible based on available binary packages? Worth trying.
I’ve put a few of the reports from pkgsrc builds on DragonFly out. They’re all using pkgsrc-2010Q1, on i386/DragonFly 2.6, i386/DragonFly 2.7, and x86_64/DragonFly 2.7. The links in the reports go to the errors that caused each package to not build. If you happen to see something that has an easy fix, or that you really need to have working, please submit a fix.
I’ve made reference to DESTDIR for pkgsrc several times, with only an informal understanding of what it means. From what I’ve learned, and what Joerg Sonnenberger’s told me, DESTDIR support means that packages can be built from pkgsrc without needing to be root. This means local packages can be built on an ordinary user account using pkgsrc.
This also means that pkgsrc can build packages before each upgrade, and only upgrade if a binary package can be built for each item involved. This means minimal downtime and no failures during upgrades, the biggest bugaboo for using pkgsrc that I’ve encountered.
The newest branch of pkgsrc for 2010 is officially out – read the release announcement for details on what’s updated. Among other things, DESTDIR support is almost complete, and a shift to default KDE4 is underway.
I’m working on bulk builds already, so hopefully soon you’ll be able to pkg_radd 2010Q1 packages…
YONETANI Tomokazu has eliminated cvsup, replacing it with net/csup from pkgsrc. The README notes that the pkgsrc package devel/cvsync is another alternative if you need to retrieve the repository and not just the checked out files..
Every time a bulk build of pkgsrc packages is completed, a report is uploaded listing what built and what didn’t. Since there’s so many reports from the now-automated build, I’ve sorted it by architecture and release, to make lookups faster.
This is handy if you’re looking to fix pkgsrc apps on DragonFly, and you need a target. It’s also a good way to see if a desired module exists as a binary.
Jan Lentfer has accomplished something rather dramatic: the removal of BIND from the base system. It’s not actually out yet, but I daresay it will be after the 2.6 release, freeing people up to install any DNS server from pkgsrc – including BIND.
The ‘freeze’ for pkgsrc-2010Q1 is scheduled to start March 16th, which will be right around the same time of the DragonFly 2.6 release. The freeze lasts 2 weeks, usually, so new packages for 2.6 will be built probably about mid-April, based on this info…
Joerg Sonnenberger announced new behavior in pkgsrc: Performing “bmake install” in pkgsrc with a package that supports DESTDIR will build a binary package and then install from that package. This means a package will be successfully build before the installation process is started, and I assume is to assist further work down the road.
Details: The old behavior was to build and install directly, which “bmake stage-install” can reproduce. DESTDIR support means that the software can be installed as non-root.
I’ve been working toward continuous builds of pkgsrc, so that there’s always up-to-date pkgsrc binaries available. I’ve been postingnotesaboutit too, which I will hopefully be able to automate soon. For example, Firefox 3.5.8, the most recent version, is already available.
In Praise of Online Obscurity – this article makes me think of communities like DragonFly and the other BSDs. In essence, growth causes smaller independent groups to form out of a larger membership, because a social group can only be maintained to a certain size. Perhaps this is why FreeBSD’s evolved a core group, or other groups form, like Wikipedia ‘editors’. (via) I’m catering to my own interests in group dynamics here.
The packages from a bulk build of pkgsrc-2009Q4, on DragonFly 2.5.1 for x86_64 have all been uploaded to avalon.dragonflybsd.org. Go ahead and upgrade using pkg_radd if you’ve got the right hardware for it.
Joerg Sonnenberger’s planning to remove more old pkgsrc packages. This includes some packages like php4, which is common and also should die. There’s discussion that can be followed from the post for some details.
I started building the pkgsrc-2009Q4 packages on several machines tonight, and I noticed something. The previous quarterly release, pkgsrc-2009Q3, had 8,969 packages. This release has 9,100. That’s right – OVER 9,000!
I’ve seen plenty of articles along the lines of “Open Source and X”, where the article explains at great length how open source in certain situations can work well. “Doing It Wrong” comes at it from a different direction.
BSD Magaine is going free, meaning it’s a free download starting with the February issue. The site says “sign up for our newsletter and get every issue straight to your inbox” – the correct link is “Newsletter” on the upper right corner of the page. PDFs of the print issues are available too.
There isn’t an official release announcement as of this moment, but the next quarterly release of pkgsrc is out. This is 2009Q4, meaning development happened in the 4th quarter of 2009. I’ll start binary package builds for DragonFly tonight…
This has been bouncing around other news outlets, but I’ll mention it here: There’s an out of data SpamAssassin rule that can potentially mark mail as spam because of the 2010 date. A mail to firstname.lastname@example.org describes the various fixes.
The step of ‘sa-update && /etc/rc.d/spamd restart’ seems to have fixed it for me. Incidentally, if you are using SpamAssassin, sa-update is a good tool to run on a regular basis.
The headline sums it up: the next quarterly release of pkgsrc, which was due on the 31st of this month, will be released at the end of the first week of January 2010. The alert message cites a number of different issues.
I have a wrapper script I use for bulk builds of pkgsrc that I think others would find usable. If you are interested in building some/all of pkgsrc to generate binary packages using pbulk, may I recommend “simplepbulk“? I’d like to see if anyone uses it on non-DragonFly systems.
Thunderbird, in pkgsrc, has been updated to version 3. This means that if you don’t want to make the upgrade right yet, you’ll want to follow mail/thunderbird2. This won’t affect binary package users until the next quarterly release.
That’s a mouthful, isn’t it? There’s a fresh build of pkgsrc packages for 32-bit DragonFly 2.4, from pkgsrc-2009Q3, on avalon.dragonflybsd.org. Utilities like pkg_radd should find it automatically. New builds for i386 2.5 and 64-bit 2.5 are on the way. (though pkgsrc packages built on 2.4 should work fine on 2.5.)
The build for pkgsrc-2009Q3 packages performed on i386 DragonFly 2.5 is complete. There’s a build log. These packages are immediately available if you are on a 2.5/i386 system and use pkg_radd. If you want to upgrade, try pkgin or pkg_rolling-replace.
Details of the new release are found in the announcement, including some biggies like KDE4. I’m building binaries for this release, for DragonFly i386/2.4, i386/2.5, and amd64/2.5. (Though the 2.5 binaries for amd64 should work on the amd64 2.4 release, too.)
The release announcement isn’t out, but the branch is there. I’m building it for DragonFly 2.4 and DragonFly 2.5 on i386 now, so we should have binary packages in about a week. I should have reports to go with it.
The next quarterly release of pkgsrc should be released by next week. Normally it is released 2 weeks after starting a freeze period, but this release was slightly delayed for some structural changes and for KDE4.
Installation of pkgsrc packages that were built on a different version of DragonFly than the one running during that installation will cause a warning. This can cause some confusion, since the tool appears to be warning that something may not work, but there’s no further output. I’ve seen users think it means the install failed, for instance.
There’s potential ways around this, but the best would be this pkg_install modification suggested by Jeremy C. Reed. Anyone who implements this gets my eternal gratitude.