public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: <nunojsilva@ist.utl.pt> (Nuno Silva)
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Binary chrome - is it safe in terms of dependencies?
Date: Thu, 31 Jan 2013 18:30:03 +0200	[thread overview]
Message-ID: <878v79gvsk.fsf@ist.utl.pt> (raw)
In-Reply-To: CAHgBc-vy9rf=UJTu4X51x1hZNyjTzH5wc3nkL034+RySjXMcyA@mail.gmail.com

On 2013-01-31, Nilesh Govindrajan wrote:

>On Jan 31, 2013 5:38 PM, "Nuno Silva" <nunojsilva@ist.utl.pt> wrote:
>
>>> Also, I suppose that, if there were library incompatibilities, the
>>> package would never go stable, or would at least, like Yohan said, lead
>>> to a block/version dependency.
>
> Well, many times you can't really anticipate everything.
>
> I had my libreoffice-bin pdf import broken for two months because some
> shared library had got upgraded against which it wasn't linked.

I guess that sometimes this kind of issues may be harder to spot, or
require harder fixes (see for example the current state of LISP where
some packages require ASDF 2 but the stable one is ASDF 1, AFAIK the
stabilization of ASDF 2 is pending because some eclasses have to be
changed), but even then I'd suppose this is what the unstable arches are
for.

-- 
Nuno Silva (aka njsg)
http://njsg.sdf-eu.org/



      reply	other threads:[~2013-01-31 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 17:39 [gentoo-user] Binary chrome - is it safe in terms of dependencies? Nilesh Govindrajan
2013-01-30 18:09 ` Yohan Pereira
2013-01-31  1:35   ` Mike Gilbert
2013-01-31  6:56     ` Nilesh Govindrajan
2013-01-31 12:08       ` [gentoo-user] " Nuno Silva
2013-01-31 12:26         ` Nilesh Govindrajan
2013-01-31 16:30           ` Nuno Silva [this message]

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=878v79gvsk.fsf@ist.utl.pt \
    --to=nunojsilva@ist.utl.pt \
    --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