pkgsrc-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
2010Q2 packages for DragonFly 2.6, 2.7 on i386 and x86_64
This is a copy of the mail I sent to the users%dragonflybsd.org@localhost
mailing
list; it notes that there's a whole bunch of binaries built for 2010Q2 and
various flavors/versions of DragonFly. I figure it's going to be of most
use to DragonFly users on that list but I've seen other "I have binaries!"
posts on the mailing list, and I need to get my act in gear. There's a
link in here to the reports, too...
--------------------------------------------------------------------------
The binary build of pkgsrc-2010Q2 is almost done.
Packages for 2.6 on i386 and x86_64 are done and uploaded:
http://avalon.dragonflybsd.org/packages/i386/DragonFly-2.6/pkgsrc-2010Q2/All/
http://avalon.dragonflybsd.org/packages/x86_64/DragonFly-2.6/pkgsrc-2010Q2/All/
Packages for 2.7/x86_64 are most of the way through uploading; it should
finish in the next day or so.
http://avalon.dragonflybsd.org/packages/x86_64/DragonFly-2.7/pkgsrc-2010Q2/All/
Packages for 2.7/i386 are only just getting started, because I was having
trouble with devel/gettext-base. It turned out that it wouldn't build
with multiple MAKE_JOBS set, so it'll probably be at least several days
before that completes. When it does finish, it will be here:
http://avalon.dragonflybsd.org/packages/i386/DragonFly-2.7/pkgsrc-2010Q2/All/
If you want to see reports on the various builds:
http://avalon.dragonflybsd.org/reports/
(Look for the 'meta' report in each directory, sorted by arch, version,
and date; e.g.
http://avalon.dragonflybsd.org/reports/i386/2.6/20100805.2342/meta/report.html
) If anyone wants to tackle the top failures causing failures in other
packages, it'd help...
For upgrading:
You can manually set pkg_radd to download from these links now, or you can
wait until they're all completely uploaded to avalon, and I'll change the
default links from 2010Q1 to 2010Q2 and you can download the newer
packages automatically.
pkg_chk or pkgin should work for upgrades, though setting them up for a
binary upgrade is more than I'm going to document here. (mostly cause I
don't know it off the top of my head.) Make sure your local /usr/pkgsrc/
is also pkgsrc-2010Q2 in case you have to build from source.
Home |
Main Index |
Thread Index |
Old Index