public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirkjan Ochtman <djc@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Over-reliance of Gentoo projects on overlays
Date: Thu, 13 Jun 2013 08:51:45 +0200	[thread overview]
Message-ID: <CAKmKYaBW0DF5UPfNZTgcVuo+rNgTWP2Kcc5Hnt+1f9n8jNfSSw@mail.gmail.com> (raw)
In-Reply-To: <CAO-1Pb6bBjADzwW6q9miUAeXt+CofSsjFx3JP-kaKj_sGAwARw@mail.gmail.com>

On Thu, Jun 13, 2013 at 6:56 AM, Alexander V Vershilov
<alexander.vershilov@gmail.com> wrote:
> The main point that haskell ecosystem is very breaky and only latest
> version is supported, so
> the safest path is to be on a bleeding edge and patch inconsistent
> applications. So if one
> package gets updated then commonly we need to fix its reversed deps,
> if it were in tree than
> we would be involved into stabilization process and in the end will
> delay updating deps, and
> the difficulty of tracking all version variant will be much higher
> than no, at the end the quality
> of the packages in tree will fall.  Really we can _guarantee_ that
> everything work in overlay
> but there is either no technical or bureaucracy reasons that prevent
> from fixing as soon as
> possible.

Still seems like working in gentoo-x86 without doing stabilization
would cover most of those bases. Working in the unstable main tree is
still a lot better than keeping stuff out there in an overlay, IMO.

Cheers,

Dirkjan


  reply	other threads:[~2013-06-13  6:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 16:51 [gentoo-dev] Over-reliance of Gentoo projects on overlays Michał Górny
2013-06-12 16:59 ` hasufell
2013-06-12 17:02   ` Ciaran McCreesh
2013-06-12 17:05     ` hasufell
2013-06-12 17:13       ` Ciaran McCreesh
2013-06-12 17:19         ` hasufell
2013-06-12 17:23         ` Michael Orlitzky
2013-06-13  4:56           ` Alexander V Vershilov
2013-06-13  6:51             ` Dirkjan Ochtman [this message]
2013-06-16  4:08               ` "Paweł Hajdan, Jr."
2013-06-16  7:36                 ` Alexander V Vershilov
2013-06-17  0:50                   ` "Paweł Hajdan, Jr."
2013-06-15  3:32             ` Michael Orlitzky
2013-06-13  5:44           ` Michał Górny
2013-06-13  8:29             ` René Neumann
2013-06-12 20:10   ` Andreas K. Huettel
2013-06-13  3:37     ` Rich Freeman
2013-06-12 20:32 ` gmt
2013-06-29 18:22 ` Thomas Kahle

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=CAKmKYaBW0DF5UPfNZTgcVuo+rNgTWP2Kcc5Hnt+1f9n8jNfSSw@mail.gmail.com \
    --to=djc@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