Bernd Steinhauser wrote:
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
I actually re-evaluated this after I sent that e-mail and changed it to
behave like cvs.eclass. Basically if you set ESVN_REPO_URI=offline, then
it'll assume you've got the revision you already want.
--
Doug Klima <[EMAIL PROTECTED]>
http://dev.gentoo.org/~cardoe/
--
gentoo-dev@lists.gentoo.org mailing list
