public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Ian Stakenvicius <axs@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [EAPI 7] The future goals for PORTDIR, ECLASSDIR and... LICENSEDIR?
Date: Sun, 22 Nov 2015 09:27:33 +0100	[thread overview]
Message-ID: <20151122092733.50da46bc.mgorny@gentoo.org> (raw)
In-Reply-To: <565102EF.4040003@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]

On Sat, 21 Nov 2015 18:49:03 -0500
Ian Stakenvicius <axs@gentoo.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 21/11/15 06:29 PM, NP-Hardass wrote:
> > Probably not the ideal solution given that you seem to prefer
> > removal of such variables, but a REPODIR variable which is set to
> > the directory where the repo is (basically making PORTDIR dynamic
> > and setting it on a per package basis) could enable developers
> > to reference their repo when needed, allowing variable use in a
> > multi repo system. Additionally, if that idea is liked, I think
> > an array of the repos masters and/or their dirs (or some
> > functions to access that information) could also be useful. Like
> > get_masters and get_repo_dir functions.
> >   
> 
> - From your description here REPODIR would only point to the current
> repo, so for licence-file access when the license is in the main
> gentoo repo, but the current repo is an overlay, it would still fail.
> 
> Similar cases could occur for eclasses, especially since 'masters'
> in repo metadata allows multiple repos to be chained.

There's also the eclass-overrides problem.

> All told, I think i'm in favour of banning the variables, and
> potentially providing getter functions that would output the path of
> these files if they need to be accessed -- '$(get_eclasspath
> [name])' or $(get_licensepath [name]) or the like.  I don't know if
> these could be implemented in-eclass or if they would be something
> that would have to be added to EAPI7..?

get_eclasspath doesn't solve the issue of storing random stuff under
eclass/ subdirectories, I think. And if I understand your idea
correctly, get_licensepath would still not work for binary packages.

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

  reply	other threads:[~2015-11-22  8:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 21:36 [gentoo-dev] [EAPI 7] The future goals for PORTDIR, ECLASSDIR and... LICENSEDIR? Michał Górny
2015-11-21 23:29 ` NP-Hardass
2015-11-21 23:49   ` Ian Stakenvicius
2015-11-22  8:27     ` Michał Górny [this message]
2015-11-23 10:51       ` Ulrich Mueller
2015-11-22  8:34     ` [gentoo-dev] " Martin Vaeth
2015-11-22  8:25   ` [gentoo-dev] " Michał Górny
2015-11-23  7:09 ` Daniel Campbell

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=20151122092733.50da46bc.mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=axs@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