public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bernd Steinhauser <gentoo@bernd-steinhauser.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] subversion.eclass
Date: Sat, 16 Feb 2008 01:11:00 +0100	[thread overview]
Message-ID: <47B62A14.8000600@bernd-steinhauser.de> (raw)
In-Reply-To: <47B622EF.9010404@gentoo.org>

Doug Klima schrieb:
>> 2) ESVN_OFFLINE which disables svn up.
>
> Isn't this a bit of a hack? The point is for it to run svn up. Now
> I've added support in a local refactor that I had started today that
> if the working copy's revision matches the requested revision, that no
> svn up is performed. Obviously the situation when you have a "live"
> SVN ebuild would still result in an svn up, but then again "live" SVN
> ebuilds are frowned upon and if the person is trying to emerge a
> "live" SVN ebuild I would expect them to always get the latest version.
What, if
- the server containing the repository doesn't respond?
- there is currently no connection to update but you need to remerge
because of new useflags added (or similar)?
In both cases with a normal merge it will die when trying to do svn up.
Of course with 1) you could hack around
that and specify the last revision in the repository, which btw. did a
svn up, too, but this was changed today.

Regards,
Bernd
-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-02-16  0:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 22:39 [gentoo-dev] subversion.eclass Bo Ørsted Andresen
2008-02-15 23:07 ` Donnie Berkholz
2008-02-16  0:05   ` Bernd Steinhauser
2008-02-15 23:40 ` Doug Klima
2008-02-16  0:11   ` Bernd Steinhauser [this message]
2008-02-16  0:28     ` Doug Klima
2008-02-16  0:11   ` Bo Ørsted Andresen
2008-02-19 20:06 ` Doug Klima
2008-02-19 21:37   ` Doug Klima
2008-02-20 16:10     ` Doug Klima
2008-02-20 16:20       ` Doug Klima
2008-02-20 16:39         ` Doug Klima

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=47B62A14.8000600@bernd-steinhauser.de \
    --to=gentoo@bernd-steinhauser.de \
    --cc=gentoo-dev@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