Thomas Sachau to...@gentoo.org writes:
Since python-3* is currently useless and not required for any package, the
dependency should by
default only pull in python-2* like this:
=dev-lang/python-2*
With that, the default way would not pull in a package, which is not needed
or used. And
On Sun, 06 Jun 2010 04:19:28 +0200
Sebastian Pipping sp...@gentoo.org wrote:
Thomas,
On 06/06/10 04:01, Thomas Sachau wrote:
[..] so even if it is not pulled in during installation, it will be
pulled in during world update.
sounds right. Preventing this requires either masking or a
On Sun, 6 Jun 2010 00:17:27 -0400
Mike Frysinger vap...@gentoo.org wrote:
i'm not saying `emake` covers all solutions you proposed, just that
the base usage isnt nearly as bleak. there are some cases where
having a wrapper around emake would be useful (such as compiling
multiple files or
Am 06.06.2010 08:36, schrieb Graham Murray:
Thomas Sachau to...@gentoo.org writes:
Since python-3* is currently useless and not required for any package, the
dependency should by
default only pull in python-2* like this:
=dev-lang/python-2*
With that, the default way would not pull in a
On 06/06/2010 12:40 PM, Thomas Sachau wrote:
My base proposal for this is something like this:
Every package defines the language(s), where it could be installed for
multiple slots, e.g.:
MULTI_SLOT=python or
MULTI_SLOT=python ruby
Additionally, it should define the supported slots,
Michał Górny wrote:
On Sun, 06 Jun 2010 04:19:28 +0200
Sebastian Pippingsp...@gentoo.org wrote:
Thomas,
On 06/06/10 04:01, Thomas Sachau wrote:
not required by any package and by default not used by
any package?
That a question I haven't seen answered before, either.
Am 06.06.2010 09:37, schrieb Michał Górny:
On Sun, 06 Jun 2010 04:19:28 +0200
Sebastian Pipping sp...@gentoo.org wrote:
Thomas,
On 06/06/10 04:01, Thomas Sachau wrote:
Since python-3* is currently useless and not required for any
package, the dependency should by default only pull in
Am 06.06.2010 13:09, schrieb Matti Bickel:
On 06/06/2010 12:40 PM, Thomas Sachau wrote:
My base proposal for this is something like this:
Every package defines the language(s), where it could be installed for
multiple slots, e.g.:
MULTI_SLOT=python or
MULTI_SLOT=python ruby
Le 06/06/2010 02:08, Sebastian Pipping a écrit :
can you explain how that happens?
Standard dependency resolution for packages with slots, there's nothing
specific about python.
Cheers,
Rémi
The current python eclass also uses some vars to specify the supported slots,
yes, but it is more
complex and harder to maintain in addition to the fact, that the dependency
part is hidden from the
package manager.
I dont think, that you can tell portage with the current implementation,
Am 06.06.2010 13:50, schrieb Domen Kožar:
The current python eclass also uses some vars to specify the supported
slots, yes, but it is more
complex and harder to maintain in addition to the fact, that the dependency
part is hidden from the
package manager.
I dont think, that you can tell
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
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
2010-06-06 12:40:28 Thomas Sachau napisał(a):
Additionally, it should define the supported slots, something like this:
SUPPORTED_RUBY_SLOTS=1.8 1.9 or
SUPPORTED_PYTHON_SLOTS=2.5 2.6 3.0 3.1
Now the package manager should take those vars and convert them to some
expanded USE vars like:
I would like to suggest that EAPI=4 be reopened for ability of using dots in
USE flag names, which was suggested in bug #311795.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
Am 06.06.2010 15:35, schrieb Domen Kožar:
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
Am 06.06.2010 15:44, schrieb Arfrever Frehtes Taifersar Arahesis:
2010-06-06 12:40:28 Thomas Sachau napisał(a):
Additionally, it should define the supported slots, something like this:
SUPPORTED_RUBY_SLOTS=1.8 1.9 or
SUPPORTED_PYTHON_SLOTS=2.5 2.6 3.0 3.1
Now the package manager should take
2010-06-06 15:54:23 Thomas Sachau napisał(a):
Am 06.06.2010 15:44, schrieb Arfrever Frehtes Taifersar Arahesis:
2010-06-06 12:40:28 Thomas Sachau napisał(a):
Additionally, it should define the supported slots, something like this:
SUPPORTED_RUBY_SLOTS=1.8 1.9 or
On Sun, 2010-06-06 at 12:40 +0200, Thomas Sachau wrote:
Every package defines the language(s), where it could be installed for
multiple slots, e.g.:
MULTI_SLOT=python or
MULTI_SLOT=python ruby
Additionally, it should define the supported slots, something like this:
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2010-06-06 23h59 UTC.
Removals:
app-text/manedit2010-06-01 15:49:30 fuzzyray
dev-java/odfdom-bin 2010-06-03 11:19:46 ali_bush
On Sun, Jun 06, 2010 at 01:35:55PM +, Domen Koooar wrote:
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
On Sun, Jun 6, 2010 at 6:54 AM, Thomas Sachau to...@gentoo.org wrote:
Am 06.06.2010 15:44, schrieb Arfrever Frehtes Taifersar Arahesis:
2010-06-06 12:40:28 Thomas Sachau napisał(a):
Additionally, it should define the supported slots, something like this:
SUPPORTED_RUBY_SLOTS=1.8 1.9 or
22 matches
Mail list logo
