a list cleaned for obvious false positives leaves the following 44 affected
packages.
i have treated ebuilds which mention FEATURES in an ewarn or einfo as
false positives although they probably should be fixed as well.
most of these have do one of the following (or a variant thereof)
hasq test
On 11-05-2009 11:26:46 +0200, Thilo Bangert wrote:
> FEATURE-misuse.txt was generated by
> $ find -name '*.ebuild' | xargs grep -nH FEATURES > FEATURES-misuse.txt
> and sifting through the false positives.
Have you checked if eclasses use it as well?
--
Fabian Groffen
Gentoo on a different leve
Hi
This question popped up while discussing how to deal with Ruby gems on
Gentoo in a way that gives the user the freedom to choose Portage,
RubyGems or both for gem management.
http://bugs.gentoo.org/show_bug.cgi?id=268857
Here's what it boils down to:
If a Ruby gem ebuild is slotted, th
Fabian Groffen said:
> On 11-05-2009 11:26:46 +0200, Thilo Bangert wrote:
> > FEATURE-misuse.txt was generated by
> > $ find -name '*.ebuild' | xargs grep -nH FEATURES >
> > FEATURES-misuse.txt and sifting through the false positives.
>
> Have you checked if eclasses use it as well?
nope - thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Schwyn wrote:
> Hi
>
> This question popped up while discussing how to deal with Ruby gems on
> Gentoo in a way that gives the user the freedom to choose Portage,
> RubyGems or both for gem management.
>
> http://bugs.gentoo.org/show_bug.cgi?id=
>
> You can't test FEATURES in an ebuild. It's portage-specific.
>
To 1) try and turn this thread into something a little more constructive
and a little less childish; and 2) help improve the tree. I present one
of the offending ebuilds dev-java/commons-io
Without posting the whole file her
We have a proposed unified qemu ebuild[1] in bugzilla that would let
users have a per-target granularity thanks to Xake.
I'm not sure if would be better have QEMU_TARGETS or separated
USER_TARGETS and SOFTMMU_TARGETS.
[1]http://bugs.gentoo.org/show_bug.cgi?id=267883
--
Luca Barbato
Gentoo
Marijn wrote:
Is it feasable to extend Portage to allow a file to be owned by
several
slots and remove it only once the last slot is uninstalled (aka: once
the ebuild is completely uninstalled)?
Do we have any guarantees that the file you want to share will be
compatible
with all gems that
Luca Barbato posted 4a082814.2050...@gentoo.org,
excerpted below, on Mon, 11 May 2009 15:28:52 +0200:
> I'm not sure if would be better have QEMU_TARGETS or separated
> USER_TARGETS and SOFTMMU_TARGETS.
Namespace pollution? QEMU_USER_TARGETS and QEMU_SOFTMMU_TARGETS, maybe?
Other than that, no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I have found an option conflict in pybugz, and I would like suggestions
for naming one of the options.
Currently we have two meanings for the --version option.
optparse wants to use --version to display the version of the program,
and we are us
Duncan wrote:
Namespace pollution? QEMU_USER_TARGETS and QEMU_SOFTMMU_TARGETS, maybe?
Right, anyway either one or two vars, anybody has a strong feeling
towards one of them or against any of them?
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_z
On Sun, 2009-05-10 at 18:56 -0400, Mark Loeser wrote:
> Sérgio Almeida said:
> > Abstract:
> >
> > Universal Select Tool is an utility to manage system configuration.
> > This tool is similar to the unmaintained eselect utility of Gentoo or
> > Exherbo's eclectic. The idea is to create a tool tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
William Hubbs :
> I'm considering changing the pybugz command syntax to be something
> similar to the way portage's syntax works. For example, "pybugz get"
> would become "pybugz --get", "post" would become "--post", etc to
> simplify the command
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
William Hubbs :
> optparse wants to use --version to display the version of the program,
> and we are using --version in the post command to set the version that
> will be part of the bug. What do you think we could use for --version
> in the pos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, May 11, 2009 at 10:13:44PM +0200, Christian Faulhammer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> William Hubbs :
> > I'm considering changing the pybugz command syntax to be something
> > similar to the way portage'
Thilo Bangert wrote:
to me, the above two contradictory viewpoints are the essence of the
apparent and real decline in Gentoo activity. The two are just not
compatible with each other and there is no clear guidance on to which of
the two should be followed.
in the one corner we have the 'Dani
On Mon, 11 May 2009 23:17:32 +0100
George Prowse wrote:
> An equilibrium seems to have been reached which currently works.
An equilibrium has been reached, agreed, but that it works is up for
debate. There is a strong argument to be made that preserving the
equilibrium will keep Gentoo the way it
Ciaran McCreesh wrote:
On Mon, 11 May 2009 23:17:32 +0100
George Prowse wrote:
An equilibrium seems to have been reached which currently works.
An equilibrium has been reached, agreed, but that it works is up for
debate. There is a strong argument to be made that preserving the
equilibrium wi
On Mon, 11 May 2009 23:29:10 +1200
Alistair Bush wrote:
> I would assume it would be better to directly test whether the user is
> root, than test that userpriv is set?
AFAIK:
if [[ ${EUID} -eq 0 ]]; then
rootstuff
else
nonrootstuff
fi
But for tests that fail with userpriv just because the
Fabian Groffen wrote:
> [snip]
> As Prefix team, we feel that the current shape of the Gentoo Prefix
> implementation is mature. That is, it has been proven to be useful for
> a number of users/scenarios, and it has been able to work for a
> substantial number of different systems, without having
On Tuesday 12 May 2009 00:31:36 Ciaran McCreesh wrote:
> On Mon, 11 May 2009 23:17:32 +0100
>
> George Prowse wrote:
> > An equilibrium seems to have been reached which currently works.
>
> An equilibrium has been reached, agreed, but that it works is up for
> debate. There is a strong argument to
21 matches
Mail list logo
