public inbox for gentoo-devhelp@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Pielmeier <billie@gentoo.org>
To: gentoo-devhelp@lists.gentoo.org
Subject: Re: [gentoo-devhelp] epatch and svn
Date: Mon, 16 Nov 2009 16:37:04 +0100	[thread overview]
Message-ID: <6142e6140911160737w495d5766g2362015d1161818a@mail.gmail.com> (raw)
In-Reply-To: <4B01698D.1090705@gmx.de>

2009/11/16 Thomas Kahle <tom111@gmx.de>:
>
> Description of this variable says:
> "List of patches to apply prior to fetching the sources". I find this
> confusing. What can you patch before you have the sources?

# @ECLASS-VARIABLE: ESVN_PATCHES
# @DESCRIPTION:
# subversion eclass can apply patches in subversion_bootstrap().
# you can use regexp in this variable like *.diff or *.patch or etc.
# NOTE: patches will be applied before ESVN_BOOTSTRAP is processed.

This is the description I read ESVN_BOOTSTRAP is not fetching the
sources it runs commands like autogen.sh and the like. So the sources
are already fetched and copied to WORKDIR.

Where did you get your description?

> Wait a minute. Now that I'm in the correct directory I source eutils
> before subversion and still have epatch available...?
> Thanks for theorizing in any case. Looking at the eclass helps a little.

Don't know, but you don't need epatch just specify ESVN_PATCHES.

-- 
Daniel Pielmeier



  reply	other threads:[~2009-11-16 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 13:36 [gentoo-devhelp] epatch and svn Thomas Kahle
     [not found] ` <6142e6140911160627x76597ca0i54f7dfdd14da1a71@mail.gmail.com>
2009-11-16 15:02   ` Thomas Kahle
2009-11-16 15:37     ` Daniel Pielmeier [this message]
2009-11-16 17:33       ` Thomas Kahle
2009-11-16 18:25         ` Mike Frysinger

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=6142e6140911160737w495d5766g2362015d1161818a@mail.gmail.com \
    --to=billie@gentoo.org \
    --cc=gentoo-devhelp@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