On 26/11/12 01:26, "C. Bergström" wrote:
> On 11/26/12 12:59 AM, Rick "Zero_Chaos" Farina wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 11/25/2012 11:47 AM, Justin wrote:
>>> Hi,
>>>
>>> I would like to introduce a new eclass for packages using the nvidia
>>> cuda compiler sui
On 11/25/2012 07:02 PM, Alec Warner wrote:
> On Sun, Nov 25, 2012 at 3:57 PM, Matthew Thode
> wrote:
>> pax_kernel is used by 21 packages. The description would generally be
>> 'make changes to the package so it works under a pax enabled kernel'.
>> Currently it is used to either patch or (inclus
On Sun, Nov 25, 2012 at 3:57 PM, Matthew Thode
wrote:
> pax_kernel is used by 21 packages. The description would generally be
> 'make changes to the package so it works under a pax enabled kernel'.
> Currently it is used to either patch or (inclusive) to pax mark.
>
> What think you?
This seems
On 11/26/12 12:59 AM, Rick "Zero_Chaos" Farina wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2012 11:47 AM, Justin wrote:
Hi,
I would like to introduce a new eclass for packages using the nvidia
cuda compiler suite. Currently the eclass simply sanitize the NVCCFLAGS.
May be ext
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2012-11-25 23h59 UTC.
Removals:
app-portage/pyGPG 2012-11-19 02:56:38 dolsen
net-im/jabberd 2012-11-20 19:19:59 hwoarang
mail-client/claw
pax_kernel is used by 21 packages. The description would generally be
'make changes to the package so it works under a pax enabled kernel'.
Currently it is used to either patch or (inclusive) to pax mark.
What think you?
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP
On 11/25/2012 09:27 PM, Lars Wendler wrote:
> Hey list,
>
> I'm planning to lastrite net-irc/xchat in the next couple of weeks.
> Unfortunately my hope that upstream development would be resumed
> didn't come true. As the code becomes more and more outdated, open
> unfixed security bugs are present
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2012 09:27 PM, Lars Wendler wrote:
> Hey list,
>
> I'm planning to lastrite net-irc/xchat in the next couple of weeks.
> Unfortunately my hope that upstream development would be resumed
> didn't come true. As the code becomes more and more ou
Am Sonntag 25 November 2012, 17:26:30 schrieb Mike Gilbert:
> On Sun, Nov 25, 2012 at 5:04 PM, Mike Frysinger wrote:
> > On Sun, Nov 25, 2012 at 3:27 PM, Lars Wendler wrote:
> >> I also planned to release a news through the portage news system as soon
> >> as I lastrite xchat so people know how to
On Sun, Nov 25, 2012 at 5:04 PM, Mike Frysinger wrote:
> On Sun, Nov 25, 2012 at 3:27 PM, Lars Wendler wrote:
>> I also planned to release a news through the portage news system as soon as I
>> lastrite xchat so people know how to move over to hexchat. As I never did
>> this
>> before I'd like to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2012 02:59 PM, Rich Freeman wrote:
> On Sun, Nov 25, 2012 at 12:55 PM, Rick "Zero_Chaos" Farina
> wrote:
>> If you have a bug on bugzie that is more than a week old and it
>> affects me, you can bet I will fix it and the notification you
>>
On Sun, Nov 25, 2012 at 3:27 PM, Lars Wendler wrote:
> I also planned to release a news through the portage news system as soon as I
> lastrite xchat so people know how to move over to hexchat. As I never did this
> before I'd like to have some help concerning this matter. Is there some
> documenta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
>> Do xchat plugins work in hexchat?
>
> That's something for me to find out as well. I maintain the
> xchat-otr plugin which I would like to continue using in hexchat.
>
just tested xchat-xsys on hexchat and it does work, all commands afais
---
Am Sonntag 25 November 2012, 22:03:03 schrieb hasufell:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/25/2012 09:27 PM, Lars Wendler wrote:
> > Hey list,
> >
> > I'm planning to lastrite net-irc/xchat in the next couple of
> > weeks. Unfortunately my hope that upstream development w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2012 09:27 PM, Lars Wendler wrote:
> Hey list,
>
> I'm planning to lastrite net-irc/xchat in the next couple of
> weeks. Unfortunately my hope that upstream development would be
> resumed didn't come true. As the code becomes more and more
>
On Sun, 25 Nov 2012 14:55:06 +0800
Patrick Lauer wrote:
> On 11/23/12 21:17, Alexis Ballier wrote:
> > On Fri, 23 Nov 2012 12:45:56 +0800
> > Patrick Lauer wrote:
> >
> >> On 11/20/12 21:57, Alexis Ballier wrote:
> >>> On Fri, 16 Nov 2012 09:10:51 + (UTC)
> >>> "Patrick Lauer (patrick)" wr
On 11/25/2012 12:27 PM, Lars Wendler wrote:
> I also planned to release a news through the portage news system as soon as I
> lastrite xchat so people know how to move over to hexchat. As I never did
> this
> before I'd like to have some help concerning this matter. Is there some
> documentatio
Hey list,
I'm planning to lastrite net-irc/xchat in the next couple of weeks.
Unfortunately my hope that upstream development would be resumed didn't come
true. As the code becomes more and more outdated, open unfixed security bugs
are present[1][2] and at some point in the future =x11-libs/gtk+
On Sun, Nov 25, 2012 at 12:55 PM, Rick "Zero_Chaos" Farina
wrote:
> If you have a bug on bugzie that
> is more than a week old and it affects me, you can bet I will fix it and
> the notification you get will be the one from me closing your bug. If
> you have an issue with that maybe you should fi
On 11/25/2012 02:14 PM, Justin wrote:
> On 25.11.2012 18:59, Rick "Zero_Chaos" Farina wrote:
>> On 11/25/2012 11:47 AM, Justin wrote:
>>> Hi,
>>
>>> I would like to introduce a new eclass for packages using the nvidia
>>> cuda compiler suite. Currently the eclass simply sanitize the NVCCFLAGS.
>>>
On 25.11.2012 18:59, Rick "Zero_Chaos" Farina wrote:
> On 11/25/2012 11:47 AM, Justin wrote:
>> Hi,
>
>> I would like to introduce a new eclass for packages using the nvidia
>> cuda compiler suite. Currently the eclass simply sanitize the NVCCFLAGS.
>> May be extended in the future.
>
>> Two prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2012 11:47 AM, Justin wrote:
> Hi,
>
> I would like to introduce a new eclass for packages using the nvidia
> cuda compiler suite. Currently the eclass simply sanitize the NVCCFLAGS.
> May be extended in the future.
>
> Two problems come up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2012 10:51 AM, Rich Freeman wrote:
> On Sun, Nov 25, 2012 at 10:43 AM, Rick "Zero_Chaos" Farina
> wrote:
>> If you horribly break my package, you may hear about it, but you
>> certainly won't get yelled at for fixing my bugs or bumping a pac
Hi,
I would like to introduce a new eclass for packages using the nvidia
cuda compiler suite. Currently the eclass simply sanitize the NVCCFLAGS.
May be extended in the future.
Two problems come up with using nvcc:
* Each version only supports a limited number of gcc versions. Therefore
we need
On Sun, Nov 25, 2012 at 10:43 AM, Rick "Zero_Chaos" Farina
wrote:
> If you horribly break my package, you may hear about it, but you
> certainly won't get yelled at for fixing my bugs or bumping a package.
While I think there is a balance to be found, keep in mind that you as
the developer aren'
On 2012.11.25 14:42, Rich Freeman wrote:
> On Sun, Nov 25, 2012 at 9:30 AM, Roy Bamford
>
> wrote:
> > From the point of view of the licencor, the licence is just as
> > important as the code, so there are no trivial licence issues.
> > As a trustee, I am unhappy with losing the traceability at a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2012 02:01 AM, Patrick Lauer wrote:
> On 11/23/12 22:32, Thomas Sachau wrote:
>> Ian Stakenvicius schrieb:
>>> On 22/11/12 11:22 PM, Robin H. Johnson wrote:
On Thu, Nov 22, 2012 at 08:22:10PM -0600, Donnie Berkholz wrote:
> On 11:11 S
On Sun, Nov 25, 2012 at 10:20 AM, Rich Freeman wrote:
> The key words are "serious" or "contact from the copyright holder."
Sorry - revise that a little:
1. Serious and they don't get a timely response from the maintainer
(or licenses@g.o).
or
2. Contact from the copyright holder.
The intent i
On Sun, Nov 25, 2012 at 10:04 AM, Ulrich Mueller wrote:
>
> But there _are_ trivial cases (e.g., most of the init script issues,
> bug 425702) where a simple ChangeLog entry would be enough for
> traceability.
I think something like that is best announced first, and then done if
there is no issue
> On Sun, 25 Nov 2012, Rich Freeman wrote:
> On Sun, Nov 25, 2012 at 9:30 AM, Roy Bamford wrote:
>> From the point of view of the licencor, the licence is just as
>> important as the code, so there are no trivial licence issues.
>> As a trustee, I am unhappy with losing the traceability at al
On Sun, Nov 25, 2012 at 9:30 AM, Roy Bamford wrote:
> From the point of view of the licencor, the licence is just as
> important as the code, so there are no trivial licence issues.
> As a trustee, I am unhappy with losing the traceability at all.
> Other trustees may have different opinions.
Not
Ole Markus With wrote:
> Maybe I could change the currently masked php5-5 slot to php5_5 instead
> and then eventually phase our the hyphen based slots. This would mean
> inconsistency between the php slots for some time, but eventual
> consistency with Python, which I do see as a good thing.
I th
On 2012.11.25 13:44, Ulrich Mueller wrote:
> > On Sun, 25 Nov 2012, hasufell wrote:
>
> > License issues seem trivial enough (at least regarding the
> > functionality of an ebuild) to be fixed without permission of the
> > actual maintainer.
>
> Certainly there are trivial license issues, bu
> On Sun, 25 Nov 2012, hasufell wrote:
> License issues seem trivial enough (at least regarding the
> functionality of an ebuild) to be fixed without permission of the
> actual maintainer.
Certainly there are trivial license issues, but not all of them are.
See bugs 436452 and 441734 for tri
The discussion came up in the thread
[gentoo-dev] open season on other-dev's packages -- policy change?
License issues seem trivial enough (at least regarding the functionality
of an ebuild) to be fixed without permission of the actual maintainer.
Even if the fix is wrong the ebuild remains intac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/24/2012 03:30 PM, Theo Chatzimichos wrote:
> Hello,
>
> We currently have values like the following: RUBY_TARGETS="ruby19"
> PHP_TARGETS="php5-3" PYTHON_TARGETS="python2_7"
>
> I find it confusing, and I would like to propose to keep the same
Hi,
Change of the unpacking logic which allows at least a speed up of factor 2.
Before we unpacked every single rpm from the tarball separately, now we
generate all possibilities and unpack them at once, ignoring warnings.
Justin
commit f13912b377189f6b80d05eb122c9f27e187c02a6
Author: Justin Lec
---
gx86/eclass/python-utils-r1.eclass | 63 ++
1 file changed, 50 insertions(+), 13 deletions(-)
diff --git a/gx86/eclass/python-utils-r1.eclass
b/gx86/eclass/python-utils-r1.eclass
index ad56919..29101b2 100644
--- a/gx86/eclass/python-utils-r1.eclass
+++ b/
38 matches
Mail list logo
