public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Zac Medico <zmedico@gentoo.org>
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH 2/2 v3] Update /usr/portage references (bug 378603)
Date: Thu, 18 Apr 2019 19:28:58 +0200	[thread overview]
Message-ID: <w6glg07p6hx.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <20190418170341.6008-1-zmedico@gentoo.org> (Zac Medico's message of "Thu, 18 Apr 2019 10:03:41 -0700")

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

>>>>> On Thu, 18 Apr 2019, Zac Medico wrote:

> --- a/man/ebuild.5
> +++ b/man/ebuild.5
> [...]
> @@ -553,8 +554,8 @@ usage.
>  .B LICENSE
>  This should be a space delimited list of licenses that the package falls
>  under.  This \fB_must_\fR be set to a matching license in
> -/usr/portage/licenses/. If the license does not exist in portage yet, you
> -must add it first.
> +/var/db/repos/gentoo/licenses/. If the license does not exist in portage
> +yet, you must add it first.

s/in portage/in the repository/

> --- a/man/portage.5
> +++ b/man/portage.5
> @@ -13,7 +13,7 @@ https://wiki.gentoo.org/wiki/Profile_(Portage)
>  .IP Note:
>  If you are looking for information on how to emerge something, please see
>  .BR emerge (1).
> -.SH "SYNOPSIS"
> +.SH "SYNOPSIS"/var/db/repos/gentoo

This change looks strange.

> [...]
> @@ -251,7 +251,7 @@ explaining how they can upgrade.
>  default-linux/x86/2005.0
>  # emerge -n '>=sys-apps/portage-2.0.51'
>  # rm -f /etc/portage/make.profile
> -# ln -s /usr/portage/profiles/default-linux/alpha/2005.0 \
> +# ln -s /var/db/repos/gentoo/profiles/default-linux/alpha/2005.0 \
>  /etc/portage/make.profile

Update the example?

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-04-18 17:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06  0:23 [gentoo-portage-dev] [PATCH 0/2] Change /usr/portage council approved locations (bug 378603) Zac Medico
2018-08-06  0:23 ` [gentoo-portage-dev] [PATCH 1/2] " Zac Medico
2018-08-06  0:23 ` [gentoo-portage-dev] [PATCH 2/2] Update /usr/portage references " Zac Medico
2018-08-06  4:59   ` Ulrich Mueller
2018-08-06  5:46     ` Zac Medico
2018-08-06  6:03       ` Zac Medico
2018-08-06  7:30       ` Brian Dolbec
2018-08-06 10:29         ` Ulrich Mueller
2018-08-06 18:35         ` Zac Medico
2018-08-06 21:50           ` M. J. Everitt
2018-08-06 22:39             ` Zac Medico
2018-08-06  5:32   ` [gentoo-portage-dev] [PATCH 2/2 v2] " Zac Medico
2018-08-06  7:44     ` Brian Dolbec
2018-08-06 18:46       ` Zac Medico
2019-04-18 17:03   ` [gentoo-portage-dev] [PATCH 2/2 v3] " Zac Medico
2019-04-18 17:28     ` Ulrich Mueller [this message]
2019-04-18 17:54       ` Zac Medico
2019-04-18 17:58   ` [gentoo-portage-dev] [PATCH 2/2 v4] " Zac Medico

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=w6glg07p6hx.fsf@kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=zmedico@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