I have bumped my ebuild for argv to version 2.6.1 To get this ebuild into your local portage tree do: And then: Enjoy.# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/dev-libs/argv /usr/local/portage/dev-libs# ACCEPT_KEYWORDS="~x86" emerge argv
I have bumped my ebuild for asn1c to version 0.9.21.
To get this ebuild into your local portage tree do:
# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/dev-util/asn1c /usr/local/portage/dev-util
And then:
# ACCEPT_KEYWORDS="~x86" emerge asn1c
Enjoy.
It has been a long time, but a new version of cvsnt is out: today 2.5.04.2911 was announced.
I have bumped my gentoo ebuild.
As always, get my ebuilds for cvsnt into your local-portage tree using rsync as follows:
# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/dev-util/cvsnt /usr/local/portage/dev-util
To install, do the usual:
# ACCEPT_KEYWORDS="~x86" emerge cvsntEnjoy!
Thanks to some help from Sebastian Schuberth, the ebuild for CVSNT has had a few tweaks and should now happily work with the latest version of Gentoo’s Portage without any of those pesky QA warnings appearing (i.e. it will now successfully emerge the package).As always, get my ebuilds for cvsnt into your local-portage tree using rsync as follows:# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/dev-util/cvsnt /usr/local/portage/dev-util
LinuxLibertine have released version 2.3.2 (read the changes in the release notes), and accordingly I’ve bumped my previous ebuild for this package to this new version.
To get the ebuild(s) for this package into your local portage tree do:
# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/media-fonts/ttf-libertine /usr/local/portage/media-fonts
Then emerge in the usual maner.
[see also gentoo bug #121217]
You can get this ebuild from the omz13 server via rsync in the usual way:
# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/www-apps/viewvc /usr/local/portage/www-apps
Remember that if you are using the wonderful lighttpd server you will have to tweak your configuration files to get it all working… if you get stuck, drop me a message via my contact page and I’ll email you some sample configuration files.
I’ve been told (by Sebastian Schuberth) that my ebuild for cvsnt-2.5.04-2471 works on the amd64 platform (when he used x86_64-pc-linux-gnu-4.1.1).
Accordingly, I’ve marked the ebuild ~amd64, and bumped it to cvsnt-2.5.04.2471-r2.ebuild.
As always, get my ebuilds for cvsnt into your local-portage tree using rsync as follows:
# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/dev-util/cvsnt /usr/local/portage/dev-util
The 2.5.04 branch of cvsnt is getting nearer to a new stable release :-)
The latest testing release, 2.5.04.2471, has been tagged, and I’ve bumped my ebuild for this release… it seems that problems with previous builds have been solved (or more accurately a workaround has been found).
As always, get my ebuilds for cvsnt using:
# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/dev-util/cvsnt /usr/local/portage/dev-util
I’ve modded the latest the ebuild for viewvc (see gentoo bug #129395) so that it works with cvsnt.
You can get this ebuild from the omz13 server via rsync in the usual way:
# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/www-apps/viewvc /usr/local/portage/www-apps
cvsnt build 2.5.04.2442 is now available, but for some reason it doesn’t compile under portage. I don’t have any time at the moment to try and resolve this issue, but do feel free to help solve this problem!
I have made the ebuild available for this release, but have hard masked it for testing (i.e. M~x86).
As always, get my ebuilds for cvsnt using:
# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/dev-util/cvsnt /usr/local/portage/dev-util