public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Domen Kožar" <domen@dev.si>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Actions of python team, especially Arfrever wrt python eclass and python-3*
Date: Sun, 06 Jun 2010 13:35:55 +0000	[thread overview]
Message-ID: <1275831355.4662.60.camel@oblak.fubar.si> (raw)
In-Reply-To: <4C0B9787.2080209@gentoo.org>

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

On Sun, 2010-06-06 at 14:41 +0200, Thomas Sachau wrote:
> Am 06.06.2010 13:50, schrieb Domen Kožar:
> >> And if you add a python slot or remove one, portage currently is not able to see that and to
> >> reinstall packages, which had modules installed for that slot. You need another tool
> >> (python-updater) to check that and to call the needed reinstalls.
> > 
> > I agree with this fact, user should not be required to read additional
> > documenation for portage to function as wanted. 
> > 
> > I'm very unfamiliar with inner workings of portage, but using
> > python-updater implementation, USE_PYTHON behaviour shouldn't be that
> > hard to implement?
> 
> You want some additional switch to portage, which does the work of python-updater? That would just
> move the code, but would still have the same limitations. What does speak against explicit user
> control for optional features/slots, including dependency handling by the package manager like in my
> proposal?
> 

Maybe I expressed myself wrong. Portage would only reuse python-updater
to detect and repair changes with python installation.

If I understand correctly, one solution would be to pull stable 2.x, and
only install other slots according to USE_PYTHON.


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

  reply	other threads:[~2010-06-06 13:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 14:33 [gentoo-dev] Actions of python team, especially Arfrever wrt python eclass and python-3* Thomas Sachau
2010-05-27 15:30 ` Gilles Dartiguelongue
2010-06-05 14:43 ` Arfrever Frehtes Taifersar Arahesis
2010-06-05 15:49   ` Thomas Sachau
2010-06-05 18:31     ` Harald van Dijk
2010-06-05 23:04       ` Thomas Sachau
2010-06-05 23:38         ` Harald van Dijk
2010-06-06  2:01           ` Thomas Sachau
2010-06-06  2:19             ` Sebastian Pipping
2010-06-06  7:37               ` Michał Górny
2010-06-06 11:14                 ` Dale
2010-06-06 11:23                 ` Thomas Sachau
2010-06-06  6:36             ` Graham Murray
2010-06-06 10:40               ` Thomas Sachau
2010-06-06 11:09                 ` Matti Bickel
2010-06-06 11:37                   ` Thomas Sachau
2010-06-06 11:50                     ` Domen Kožar
2010-06-06 12:31                       ` Thomas Sachau
2010-06-06 12:41                       ` Thomas Sachau
2010-06-06 13:35                         ` Domen Kožar [this message]
2010-06-06 13:51                           ` Thomas Sachau
2010-06-07  1:22                           ` Brian Harring
2010-06-06 13:44                 ` Arfrever Frehtes Taifersar Arahesis
2010-06-06 13:54                   ` Thomas Sachau
2010-06-06 14:07                     ` Arfrever Frehtes Taifersar Arahesis
2010-06-07  5:53                     ` Alec Warner
2010-06-06 16:36                 ` Hans de Graaff
2010-06-06  0:08         ` Sebastian Pipping
2010-06-06 11:48           ` Rémi Cardona
2010-06-05 20:06   ` Sebastian Pipping

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=1275831355.4662.60.camel@oblak.fubar.si \
    --to=domen@dev.si \
    --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