From: Marco Matthies <marco-ml@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Subversion 1.2
Date: Thu, 14 Jul 2005 19:26:33 +0200 [thread overview]
Message-ID: <42D6A049.8080609@gmx.net> (raw)
In-Reply-To: <42D6859E.6050406@shic.co.uk>
Steve [Gentoo] wrote:
> I'd have thought lots of people in the gentoo crowd would have been
> eagerly awaiting subversion 1.2.x with its substantial new "reserved
> checkout" - but nothing seems to have moved forward.
you must have missed this link from the gentoo homepage (on the left):
http://packages.gentoo.org/
a search yields this:
http://packages.gentoo.org/search/?sstring=subversion
also, for a command-line version, read:
man equery
You might also want to read up on the portage section in the gentoo
handbook:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3
sorry for such a canned answer, but i would only repeat what's been
written there.
> I've tried using ~x86 as my USE flag - but the 1.2 ebuild still won't
> install reporting a "Problem in dev-util/subversion-1.2 dependencies"...
> I'm reluctant to use an unstable subverison port as it would cost me a
> fair bit of time if it scrambles my version controlled files. Does
> anyone know what the problems are and why its taking so long to get
> 1.2.x into the default portage tree?
Don't put ~x86 in your USE flags just for that - use
/etc/portage/package.keywords (see the above mentioned portage guide).
I'm not exactly sure what you want - Gentoo leaves packages in unstable
for a default period of time to make sure they work allright. If you
want the newest version of a package, you must tell portage to do so by
putting the appropriate stuff (subversion and it's dependencies) in
/etc/portage/package.keywords.
Here, i just did it myself by putting this in my package.keywords
(create this file if it doesn't exist) :
=dev-util/subversion-1.2.1 ~x86
=dev-libs/apr-util-0.9.5 ~x86
=dev-libs/apr-0.9.5 ~x86
You just add one package, ask portage to merge, then put in the next
dependency, and so on...
Tried this on amd64 (with ~amd64 instead of ~x86, naturally), it's
happily compiling away... This was just info about portage, it is in no
way any form of endorsement on the new version of subversion, as I
haven't used it at all - and I don't know if you should be so impatient
with a new version of a package that seems to be important to you and
your data...
Hope this helps,
Marco
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-14 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 15:32 [gentoo-user] Subversion 1.2 Steve [Gentoo]
2005-07-14 17:02 ` Kurt Guenther
2005-07-14 17:26 ` Marco Matthies [this message]
2005-07-14 18:20 ` Steve [Gentoo]
2005-07-14 18:35 ` Petteri Räty
2005-07-14 19:48 ` Steve [Gentoo]
2005-07-14 20:58 ` Holly Bostick
2005-07-15 14:55 ` Steve [Gentoo]
2005-07-15 15:18 ` Zac Medico
2005-07-14 23:12 ` Marco Matthies
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42D6A049.8080609@gmx.net \
--to=marco-ml@gmx.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox