public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Lastrites: media-gfx/picasa, dev-python/papyon, net-voip/telepathy-butterfly, sci-visualization/paraview, x11-misc/xdaf
Date: Sun, 10 Feb 2013 12:59:09 +0100	[thread overview]
Message-ID: <1360497549.26312.7.camel@belkin4> (raw)
In-Reply-To: <511788EE.1010307@gentoo.org>

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

El dom, 10-02-2013 a las 19:47 +0800, Patrick Lauer escribió:
> On 02/10/2013 05:01 PM, Pacho Ramos wrote:
> > # Pacho Ramos <pacho@gentoo.org> (10 Feb 2013)
> > # Fails with gcc-4.7, crashes (#301946, #312073), problems with
> > # boost (#319921), problems with python-2.7 (#338826), really old
> > # version in the tree, people should move to sci overlay one (#424659).
> > # Removal in a month.
> > sci-visualization/paraview
> 
> So instead of moving things from random overlays to the tree we remove
> packages now, remove features from other packages because of that
> (openfoam) and then ... tell users to use an overlay?
> 
> Somehow this appears not well thought out to me. Would anyone be
> terribly upset if I started pillaging this silly overlay? (And any other
> overlays that look like they are fun)
> 

That is because looks nobody from sci team has enough time to move
things from sci overlay to the tree (probably because it's being
maintained there by people without commit access). Ideally that people
would become devs with commit rights but, until then, looks like some
packages (usually sci maintained packages) are being maintained better
in overlay than main tree :/

I guess wouldn't be problems on pillaging ebuilds from that overlay to
the tree... but I guess you would be willing to become its maintainer to
update ebuilds from overlay when needed :|

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-02-10 11:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  9:01 [gentoo-dev] Lastrites: media-gfx/picasa, dev-python/papyon, net-voip/telepathy-butterfly, sci-visualization/paraview, x11-misc/xdaf Pacho Ramos
2013-02-10 11:47 ` Patrick Lauer
2013-02-10 11:48   ` Michał Górny
2013-02-10 12:11     ` Rich Freeman
2013-02-10 15:10       ` Ben de Groot
2013-02-10 16:18         ` Rich Freeman
2013-02-10 11:59   ` Pacho Ramos [this message]
2013-02-10 15:05     ` hasufell
2013-02-10 15:08       ` Pacho Ramos
2013-02-10 15:59       ` Peter Stuge
2013-02-10 12:12   ` Tomáš Chvátal
2013-02-10 15:48     ` Peter Stuge
2013-02-10 18:34       ` Alec Warner
2013-02-10 19:50         ` Peter Stuge
2013-02-10 12:51   ` Alexander Berntsen
2013-02-10 13:26     ` Rich Freeman
2013-02-10 14:37     ` Tomáš Chvátal
2013-02-10 14:49       ` Rich Freeman
2013-02-10 14:42 ` [gentoo-dev] Re: [gentoo-dev-announce] " hasufell
2013-02-10 20:21 ` James Cloos

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=1360497549.26312.7.camel@belkin4 \
    --to=pacho@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