From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: bzr.eclass
Date: Tue, 24 Feb 2009 04:18:08 -0800 [thread overview]
Message-ID: <20090224121808.GA3506@hrair> (raw)
In-Reply-To: <20090223204528.636b5be9@terra.solaris>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On Mon, Feb 23, 2009 at 08:45:28PM +0100, Christian Faulhammer wrote:
> > if [[ ${EBZR_REPO_URI} == */* ]]; then
> > repository="${EBZR_REPO_URI}/${EBZR_BRANCH}"
> > elif [[ -n ${EBZR_BRANCH} ]] ; then
> > ...
> > else
> > ...
> > fi
> >
> > If I see this correctly, this appends EBZR_BRANCH if there is a slash
> > in the REPO_URI ... what kind of guess is this supposed to be? I
> > think, the second test (append iff EBZR_BRANCH is set) should be
> > sufficient.
>
> Not sure, though I will investigate (and likely drop it).
Kindly drop that; the REPO_URI/BRANCH seperation that is in use there
really isn't all that useful for bzr ebuilds in my experience- more
often then not it winds up biting me in the ass rather then being
useful.
My usage (and understanding of bzr), there isn't a scenario where
seperation of the repo and branch applies- you only need the branch
uri, that encompasses it all (unlike cvs, where this probably was
inherited from).
So... any reason to even have the var seperation like that?
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-24 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 12:21 [gentoo-dev] bzr.eclass Christian Faulhammer
2009-02-14 15:37 ` Ulrich Mueller
2009-02-14 16:15 ` [gentoo-dev] bzr.eclass Christian Faulhammer
2009-02-14 18:19 ` [gentoo-dev] bzr.eclass Jorge Manuel B. S. Vicetto
2009-02-15 6:49 ` Donnie Berkholz
2009-02-19 8:59 ` [gentoo-dev] bzr.eclass Christian Faulhammer
2009-02-19 9:26 ` Ulrich Mueller
2009-02-19 9:42 ` Nirbheek Chauhan
2009-02-19 15:39 ` Petteri Räty
2009-02-19 15:39 ` Nirbheek Chauhan
2009-02-19 16:01 ` Petteri Räty
2009-02-19 23:11 ` Christian Faulhammer
2009-02-20 7:00 ` Ulrich Mueller
2009-02-23 19:40 ` Christian Faulhammer
2009-02-19 8:52 ` Christian Faulhammer
2009-02-20 12:30 ` [gentoo-dev] bzr.eclass René 'Necoro' Neumann
2009-02-23 19:45 ` [gentoo-dev] bzr.eclass Christian Faulhammer
2009-02-24 12:18 ` Brian Harring [this message]
2009-03-02 7:33 ` Christian Faulhammer
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=20090224121808.GA3506@hrair \
--to=ferringb@gmail.com \
--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