public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Permissions error on starting X.
Date: Mon, 5 Nov 2018 11:35:01 -0500	[thread overview]
Message-ID: <CAGfcS_=SWwjp8at9VTB++70a4U9MQUXbT6nd8tOXynWQA7pq0w@mail.gmail.com> (raw)
In-Reply-To: <prpqt4$iqu$1@blaine.gmane.org>

On Mon, Nov 5, 2018 at 11:27 AM Nikos Chantziaras <realnc@gmail.com> wrote:
>
> On 05/11/2018 17:30, Grant Edwards wrote:
> > On 2018-11-04, Nikos Chantziaras <realnc@gmail.com> wrote:
> >> On 03/11/2018 16:01, Alan Mackenzie wrote:
> >>> The developers, in this instance, failed to raise the ebuild's version
> >>> number from 1.20.3 when making this change, and also didn't notify users
> >>> by a NEWS item, that I can see.
> >>
> >> Emerge will catch this, no need for revbump. Unless you're not using -D
> >> (--deep) when updating world. Which you should.
> >
> > What do you mean "catch this"?
> >
> > I always use -D, and the change broke my system.
>
> I mean that a USE flag change will trigger a rebuild of the package

-D will not cause USE flag changes to trigger a rebuild of a package.

You're thinking of --newuse in this particular case.  I'm not sure if
--changed-use would cause a rebuild if the previous flag was defaulted
to enabled and not explicitly enabled (of course, if it were
explicitly enabled you wouldn't have run into this issue).

-- 
Rich


  reply	other threads:[~2018-11-05 16:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 14:01 [gentoo-user] Permissions error on starting X Alan Mackenzie
2018-11-03 14:46 ` Rich Freeman
2018-11-03 23:17 ` Neil Bothwick
2018-11-04 18:39   ` Alarig Le Lay
2018-11-04  1:11 ` [gentoo-user] " Nikos Chantziaras
2018-11-04 10:22   ` Neil Bothwick
2018-11-04 16:04     ` Daniel Frey
2018-11-05 15:30   ` Grant Edwards
2018-11-05 16:27     ` Nikos Chantziaras
2018-11-05 16:35       ` Rich Freeman [this message]
2018-11-05 16:43         ` Nikos Chantziaras
2018-11-04  6:20 ` [gentoo-user] " Daniel Frey
2018-11-04 18:33   ` tuxic
2018-11-04 19:18     ` Neil Bothwick
2018-11-05  4:06       ` tuxic
2018-11-05  8:17         ` Neil Bothwick
2018-11-04 20:02     ` Daniel Frey
2018-11-05 15:29 ` [gentoo-user] " Grant Edwards
2018-11-07  3:59 ` [gentoo-user] " YUE Daian
2018-11-09  0:20   ` Hervé Guillemet
2018-11-09  8:49     ` gevisz
2018-11-09  9:19       ` YUE Daian
2018-11-09 10:24         ` Hervé Guillemet
2018-11-08 20:47 ` gevisz
2018-11-08 21:23   ` gevisz

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='CAGfcS_=SWwjp8at9VTB++70a4U9MQUXbT6nd8tOXynWQA7pq0w@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@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