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: [gentoo-dev] Allow variable refs in HOMEPAGE
Date: Thu, 3 Aug 2017 11:33:04 -0400	[thread overview]
Message-ID: <CAJ0EP43wRJ3GyKKJhK_M-023dW=3WJugQrrqBh1BkKDWG0zBxg@mail.gmail.com> (raw)

I would like to remove the ban on variable references in the HOMEPAGE
variable in ebuilds.

As I understand it, this ban was put in place so that people can
easily copy/paste from an ebuild to a web browser.

If people want to copy/paste the URL, they can easily query the final
value using the portage API, or a tool written against it.

% equery m www-client/chromium
 * www-client/chromium [gentoo]
Maintainer:  chromium@gentoo.org (Chromium in Gentoo Project)
Upstream:    None specified
Homepage:    http://chromium.org/
Location:    /home/floppym/repos/gentoo/www-client/chromium
Keywords:    59.0.3071.104:0: x86
Keywords:    60.0.3112.40:0:
Keywords:    60.0.3112.78:0: amd64
Keywords:    61.0.3159.5:0:
Keywords:    61.0.3163.13:0: ~amd64 ~arm ~arm64 ~x86
License:     BSD

Allowing variables in HOMEPAGE would allow for easier copying of
similar/identical ebuilds. For example, see the trivial ebuilds in my
overlay below.

https://bitbucket.org/floppym/floppym-overlay/src/8b55fab291ec1f9be93ade9c91e7d62d7b8a259d/dev-go/cloudflare-go/cloudflare-go-0.7.4.ebuild

https://bitbucket.org/floppym/floppym-overlay/src/8b55fab291ec1f9be93ade9c91e7d62d7b8a259d/dev-go/pkg-errors/pkg-errors-0.8.0.ebuild

https://bitbucket.org/floppym/floppym-overlay/src/8b55fab291ec1f9be93ade9c91e7d62d7b8a259d/dev-go/urfave-cli/urfave-cli-1.19.1.ebuild


             reply	other threads:[~2017-08-03 15:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 15:33 Mike Gilbert [this message]
2017-08-03 15:54 ` [gentoo-dev] Allow variable refs in HOMEPAGE Michał Górny
2017-08-03 20:56   ` Mike Gilbert
2017-08-03 23:10   ` Sam Jorna
2017-08-03 17:21 ` Jonas Stein
2017-08-07 14:05   ` Kent Fredric
2017-08-03 18:21 ` Michael Orlitzky
2017-08-03 18:32   ` Michał Górny
2017-08-03 18:57   ` Mike Gilbert
2017-08-03 19:12     ` Michael Orlitzky
2017-08-03 19:39       ` Mike Gilbert
2017-08-03 19:56         ` Michael Orlitzky
2017-08-03 20:46           ` Mike Gilbert
2017-08-03 22:33           ` Ulrich Mueller
2017-08-04  3:24             ` Michael Orlitzky
2017-08-04  6:50               ` Michał Górny
2017-08-04 13:43                 ` Michael Orlitzky
2017-08-04 14:02                   ` Peter Stuge
2017-08-04  6:51               ` Ulrich Mueller
2017-08-03 19:39   ` Ulrich Mueller
2017-08-03 19:34 ` Ulrich Mueller

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='CAJ0EP43wRJ3GyKKJhK_M-023dW=3WJugQrrqBh1BkKDWG0zBxg@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