public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dependency conflict.  openjpeg  ffmpeg
Date: Sun, 15 Jun 2014 03:59:25 -0500	[thread overview]
Message-ID: <539D606D.3050609@gmail.com> (raw)
In-Reply-To: <20140615094624.523d11ef@digimed.co.uk>

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

Neil Bothwick wrote:
> On Sun, 15 Jun 2014 00:10:41 -0500, Dale wrote:
>
>> Ahh.  I was curious and thought about that.  That version is mentioned
>> in the error tho so I wasn't sure.  I wonder tho, can I add that file
>> and not have a version at all?   Sort of like I do in package.keywords
>> etc etc.
>
> You can, but you just said.
>
>> I've
>> never put anything in the env directory before and would prefer to keep
>> it that way because I will forget it is there and it will come back and
>> bite me some day. 
>
> Using the version number means the setting will "expire" when the
> package is upgraded, meaning it won;t be able to bite you later on.
>
> Though I would prefix the atom with ~ instead of = to cover patch level
> updates.
>
>

I have looked for a place where it is documented how to do that.  I know
there is a lot of ways to add packages to those files with <=> and such
in front of the package names.  Do you have a link to some docs on
that?   If not, some examples would be cool.

Well, I was going to try adding the variable to make.conf as posted in
another email.  I think that may be better since this seems to be a
issue that is "in flux" at the moment.  ;-)

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 2012 bytes --]

  reply	other threads:[~2014-06-15  8:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 21:23 [gentoo-user] Dependency conflict. openjpeg ffmpeg Dale
2014-06-14 23:00 ` Alan McKinnon
2014-06-15  0:12   ` Dale
     [not found]   ` <EQDB1o00e1kktTk01QDC7q>
2014-06-15  1:20     ` John Campbell
2014-06-15  2:10       ` Dale
     [not found]       ` <ESAJ1o00S1kktTk01SAKbb>
2014-06-15  2:31         ` John Campbell
2014-06-15  5:10           ` Dale
2014-06-15  8:46             ` Neil Bothwick
2014-06-15  8:59               ` Dale [this message]
2014-06-15  9:09                 ` Neil Bothwick
2014-06-15 10:29                   ` Dale
     [not found]           ` <EVAt1o00G1kktTk01VAu3p>
2014-06-15  6:13             ` John Campbell
2014-06-15  6:40               ` wraeth
2014-06-15  6:56                 ` wraeth
2014-06-15  8:47               ` Dale
2014-06-16  7:43                 ` [gentoo-user] " Jonathan Callen
2014-06-17 23:43       ` [gentoo-user] " Dale
2014-06-19 22:03         ` Dale
2014-06-17 15:56 ` thegeezer
2014-06-17 21:10   ` Dale

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=539D606D.3050609@gmail.com \
    --to=rdalek1967@gmail.com \
    --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