public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] ebuild-writing/variables: better describe ROOT
Date: Sun, 15 May 2016 23:09:34 -0400	[thread overview]
Message-ID: <CAJ0EP42CAGB9q=epsaXwQy6iz7xW6ryqdzhrzG4JKpwWHJdtVg@mail.gmail.com> (raw)
In-Reply-To: <57379A09.2010203@binghamton.edu>

On Sat, May 14, 2016 at 5:35 PM, Göktürk Yüksek <gokturk@binghamton.edu> wrote:
> Mike Gilbert:
>> The current description of ROOT makes no sense and just confuses
>> people. The new description is paraphrased from PMS. ---
>> ebuild-writing/variables/text.xml | 5 +++-- 1 file changed, 3
>> insertions(+), 2 deletions(-)
>>
>> diff --git a/ebuild-writing/variables/text.xml
>> b/ebuild-writing/variables/text.xml index ef15347..6ba6379 100644
>> --- a/ebuild-writing/variables/text.xml +++
>> b/ebuild-writing/variables/text.xml @@ -100,8 +100,9 @@ them. <tr>
>> <ti><c>ROOT</c></ti> <ti> -      Path to the root directory. When
>> not using <c>${D}</c>, -      always prepend <c>${ROOT}</c> to the
>> path. +      The absolute path to the root directory into which the
>> package is to be merged. +      Use this when refering to installed
>> files in <c>pkg_*</c> functions. +      Never use this in
>> <c>src_*</c> functions. </ti> </tr> <tr>
>>
>
> Sorry for the late reply. There is actually a bug for this issue [0].
> I'll rebase the patch attached to the bug on top of yours if you have
> no technical objections to the content.
>
> [0] https://bugs.gentoo.org/show_bug.cgi?id=144332

The expanded explanation seems useful indeed.


      reply	other threads:[~2016-05-16  3:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-08 17:42 [gentoo-dev] [PATCH] ebuild-writing/variables: better describe ROOT Mike Gilbert
2016-05-10 15:08 ` Michael Orlitzky
2016-05-10 15:22   ` M. J. Everitt
2016-05-10 18:28   ` Mike Gilbert
2016-05-10 19:57     ` James Le Cuirot
2016-05-10 21:25     ` Michael Orlitzky
2016-05-10 21:27       ` Ian Stakenvicius
2016-05-11  1:42       ` Mike Gilbert
2016-05-11  1:54         ` Brian Dolbec
2016-05-11  2:40           ` Mike Gilbert
2016-05-11  2:50             ` Brian Dolbec
2016-05-11  2:19         ` Mike Gilbert
2016-05-11  2:38           ` Mike Gilbert
2016-05-14 21:35 ` Göktürk Yüksek
2016-05-16  3:09   ` Mike Gilbert [this message]

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='CAJ0EP42CAGB9q=epsaXwQy6iz7xW6ryqdzhrzG4JKpwWHJdtVg@mail.gmail.com' \
    --to=floppym@gentoo.org \
    --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