On Thu, 1 Nov 2012 07:21:38 +0100
Peter Stuge wrote:
> Graham Murray wrote:
> > > Christ on a $#@%! crutch. You can NOT auto-enable C++11 in your library
> > > based
> > > on a configure test and then stuff flags that are not supported by
> > > previous
> > > compiler versions into pkg-config
On 31/10/2012 23:42, Peter Stuge wrote:
> Can you clarify? Do you propose that developers carry out wild
> experiments by committing things that probably don't work and
> masking them?
Dirty experiments, no. Testing stuff that's almost ready, yes. If you
run the tinderbox against dirty experiments
Diego Elio Pettenò wrote:
> > Um, so how come an overlay isn't the obvious method for testing,
> > before putting things in the main tree? What other method is *more*
> > convenient for testing?
>
> package.mask
Can you clarify? Do you propose that developers carry out wild
experiments by committ
Ryan Hill wrote:
> You can NOT
I am not saying that it is a good idea, but of course you can. It has
pretty sucky effects on how your library can be used, disabling
various smart stuff that modern systems do, but I guess the upstream
practises may be from a different time.
> Somebody sane please
On 31/10/2012 23:18, Peter Stuge wrote:
> Um, so how come an overlay isn't the obvious method for testing,
> before putting things in the main tree? What other method is *more*
> convenient for testing?
package.mask
> Diego, I would like to ask you to step off Arfrever.
And I would like that dev
Graham Murray wrote:
> > Christ on a $#@%! crutch. You can NOT auto-enable C++11 in your library
> > based
> > on a configure test and then stuff flags that are not supported by previous
> > compiler versions into pkg-config for library consumers. Somebody sane
> > please fix this.
>
> Though i
Diego Elio Pettenò wrote:
> > One of major problems with this tinderbox is that it cannot be
> > used to test packages against newer versions of packages present
> > in overlays [1]
>
> Which is not a problem since we're _not_ talking about packages
> in overlays but of a bump in the main tree whi
On 31/10/2012 23:13, Graham Murray wrote:
> Though is it not normally a reasonable assumption that the library
> consumers will be built with the same or later compiler version as the
> library? In which case it does no harm.
Not really, it's not.
--
Diego Elio Pettenò — Flameeyes
flamee...@flam
Ryan Hill writes:
> Christ on a $#@%! crutch. You can NOT auto-enable C++11 in your library based
> on a configure test and then stuff flags that are not supported by previous
> compiler versions into pkg-config for library consumers. Somebody sane
> please fix this.
Though is it not normally
On Wed, Oct 31, 2012 at 5:54 AM, Rich Freeman wrote:
> On Wed, Oct 31, 2012 at 8:31 AM, Dirkjan Ochtman wrote:
>>
>> If you're going to file bugs "in a semi-automated manner", might as
>> well try to assign to the correct maintainer?
>
> How about a policy - no automated bugs may be logged to the
On Mon, 29 Oct 2012 15:39:14 -0400
Alexandre Rostovtsev wrote:
> On Mon, 2012-10-29 at 11:35 -0700, Diego Elio Pettenò wrote:
> > The problem with ICU is worse than you expect. For once, with version
> > 50, it changes ABI (but not soname as far as I can tell) depending on
> > which compiler you
Quoting Chris Reffett (2012-10-31 16:17:20)
> > Yep he should've assign them, but anyway the annoying elog messages
> > are an issue. And quite few packages suffer from it :-)
It would actually be hard to find useful message which place is in elog
showing up every install. Why not move such thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
# Chí-Thanh Christopher Nguyễn (31 Oct 2012)
# Build and runtime issues, bugs #340883, #369385, #435444.
# If you require a graphical monitor configuration tool and your desktop
# environment doesn't provide any, try x11-misc/arandr or lxde-base/lxran
On Wed, Oct 31, 2012 at 7:02 PM, Ciaran McCreesh
wrote:
> On Wed, 31 Oct 2012 17:26:38 +0100
> Theo Chatzimichos wrote:
>> +1 and btw move the devmanual in the wiki :D
>
> That would rather go against the original idea behind the devmanual,
> which was that it was supposed to be high quality and
On Wed, Oct 31, 2012 at 3:36 PM, Samuli Suominen wrote:
> On 31/10/12 17:09, Michał Górny wrote:
>>
>> On Wed, 31 Oct 2012 11:57:49 -0300
>> Alexis Ballier wrote:
>>
>>> On Tue, 30 Oct 2012 21:18:02 +0100
>>> Michał Górny wrote:
>>> [...]
Don't even try to touch any of my eclasses with
On Wed, Oct 31, 2012 at 3:02 PM, Ciaran McCreesh
wrote:
>
> On Wed, 31 Oct 2012 17:26:38 +0100
> Theo Chatzimichos wrote:
> > +1 and btw move the devmanual in the wiki :D
>
> That would rather go against the original idea behind the devmanual,
> which was that it was supposed to be high quality a
On Wed, Oct 31, 2012 at 02:18:42pm +0100, li...@aixah.de wrote:
> maybe you should remember that non-devs simply /aren't allowed/ to
> assign bugs correctly...
That is not correct. I am no dev and i do have edit-bugs privileges.
They were given to me on request by a developer from a project i am
On Wed, 31 Oct 2012 17:26:38 +0100
Theo Chatzimichos wrote:
> +1 and btw move the devmanual in the wiki :D
That would rather go against the original idea behind the devmanual,
which was that it was supposed to be high quality and authoritative.
--
Ciaran McCreesh
signature.asc
Description: PG
On 31/10/2012 11:49, Michał Górny wrote:
> In other words, you have thrown a big, destructive change to live,
> stable systems without prior testing (and don't say you were able to
> test it thoroughly in one day's time) and you have left them for other
> people to maintain and fix.
>
> I am reall
On Wed, 31 Oct 2012 16:32:25 + (UTC)
"Diego Petteno (flameeyes)" wrote:
> flameeyes12/10/31 16:32:25
>
> Modified: boost-1.46.1-r1.ebuild metadata.xml
> boost-1.49.0-r1.ebuild ChangeLog
> Added:boost-1.51.0-r1.ebuild
> Removed:
On 31/10/12 20:17, Rich Freeman wrote:
On Wed, Oct 31, 2012 at 12:15 PM, Samuli Suominen wrote:
eclass/ handling should go to repoman and the automated ChangeLog process,
should be rather straight forward for knowing person.
Perhaps, but right now the policy is to update it, so do it. The
po
On Wed, Oct 31, 2012 at 12:15 PM, Samuli Suominen wrote:
> eclass/ handling should go to repoman and the automated ChangeLog process,
> should be rather straight forward for knowing person.
Perhaps, but right now the policy is to update it, so do it. The
policy is also to post eclass changes for
On Wed, 31 Oct 2012 12:26:14 -0400
Ian Stakenvicius wrote:
> I agree, that'd make the whole thing easier. But until repoman can
> commit in eclass/ it shouldn't be that hard to just run echangelog ,
> as "inefficient" as that may be. :)
https://bugs.gentoo.org/show_bug.cgi?id=390651
jer
On Wed, 31 Oct 2012 12:26:14 -0400
Ian Stakenvicius wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 31/10/12 12:15 PM, Samuli Suominen wrote:
> > On 31/10/12 17:39, Alexis Ballier wrote:
> >> On Wed, 31 Oct 2012 11:35:41 -0400 Ian Stakenvicius
> >> wrote:
> >>
> >>> -BEGI
On Wed, Oct 31, 2012 at 1:39 PM, Michael Palimaka wrote:
> Hi all,
>
> In bug #304435[1], hwoarang suggested merging the devrel handbook[2] into
> the devmanual[3].
>
> As the project has grown, so has the amount - and dispersion - of
> development information. I believe consolidation of this info
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/10/12 12:15 PM, Samuli Suominen wrote:
> On 31/10/12 17:39, Alexis Ballier wrote:
>> On Wed, 31 Oct 2012 11:35:41 -0400 Ian Stakenvicius
>> wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
>>> On 31/10/12 11:26 AM, Alexis Ba
On 31/10/12 17:04, Alexis Ballier wrote:
On Tue, 30 Oct 2012 23:22:01 +0200
Samuli Suominen wrote:
[...]
One of the commits was before anything was said to ML (the EAPI
change), the comment was later but the commenter didn't notice it
just got fixed minutes before that.
I didn't ignore anythin
Le mercredi 31 octobre 2012 à 18:08 +0200, Samuli Suominen a écrit :
> On 31/10/12 10:56, Fabian Groffen wrote:
> > On 31-10-2012 09:51:51 +0200, Samuli Suominen wrote:
> >> I don't do prefix and I'm _always_ expecting a patch from prefix@ for
> >> prefix issues.
> >
> > In that case, please don't
On 31/10/12 17:39, Alexis Ballier wrote:
On Wed, 31 Oct 2012 11:35:41 -0400
Ian Stakenvicius wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/10/12 11:26 AM, Alexis Ballier wrote:
On Tue, 30 Oct 2012 18:39:44 -0600 Ryan Hill
wrote: [...]
The file is pointless if not everyone is
On 31/10/12 10:56, Fabian Groffen wrote:
On 31-10-2012 09:51:51 +0200, Samuli Suominen wrote:
I don't do prefix and I'm _always_ expecting a patch from prefix@ for
prefix issues.
In that case, please don't invent prefix things yourself. Thanks.
Thank you for reviewing the eclass. The pref
On 10/31/2012 10:05 AM, Rich Freeman wrote:
> On Wed, Oct 31, 2012 at 9:18 AM, wrote:
>> Maybe you should remember that non-devs simply /aren't allowed/ to
>> assign bugs correctly...
>>
>> And if you look closer into these bugs, you might discover that jer
>> instructed this guy to file separate
On Wed, 31 Oct 2012 13:49:37 +0100
Dirkjan Ochtman wrote:
> Though if you don't know these kinds of basics, I'm not sure you
> should be doing *any* (semi- or not) automated bug filing.
What if you don't have the privilege to assign bugs, but are willing to
do the work of filing the bugs?
On 31/10/12 17:09, Michał Górny wrote:
On Wed, 31 Oct 2012 11:57:49 -0300
Alexis Ballier wrote:
On Tue, 30 Oct 2012 21:18:02 +0100
Michał Górny wrote:
[...]
Don't even try to touch any of my eclasses without prior asking.
A bit aggressive but its rather obvious that this is the norm not th
On Wed, 31 Oct 2012 11:35:41 -0400
Ian Stakenvicius wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 31/10/12 11:26 AM, Alexis Ballier wrote:
> > On Tue, 30 Oct 2012 18:39:44 -0600 Ryan Hill
> > wrote: [...]
> >>> The file is pointless if not everyone is using it. I've
> >>> of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/10/12 11:26 AM, Alexis Ballier wrote:
> On Tue, 30 Oct 2012 18:39:44 -0600 Ryan Hill
> wrote: [...]
>>> The file is pointless if not everyone is using it. I've
>>> offered to remove the file before, and I'm reoffering to do so
>>> now.
>>
>>
On 31/10/2012 05:39, Michael Palimaka wrote:
>
>
> In bug #304435[1], hwoarang suggested merging the devrel handbook[2]
> into the devmanual[3].
+1 it was on my TODO list for over two years at this point.
--
Diego Elio Pettenò — Flameeyes
flamee...@flameeyes.eu — http://blog.flameeyes.eu/
On Tue, 30 Oct 2012 18:39:44 -0600
Ryan Hill wrote:
[...]
> > The file is pointless if not everyone is using it. I've offered to
> > remove the file before, and I'm reoffering to do so now.
>
> It's pointy enough for most uses. Let's keep it that way.
I would like to know what are those uses.
On Wed, Oct 31, 2012 at 1:39 PM, Michael Palimaka wrote:
> What do you think?
+1 love it. The split is pretty annoying, it would be great to have
everything in one place.
Cheers,
Dirkjan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/31/2012 08:52 AM, Tomáš Chvátal wrote:
> 2012/10/31 Dirkjan Ochtman :
>> That's rather unsurprising...
>>
>> If you're going to file bugs "in a semi-automated manner", might
>> as well try to assign to the correct maintainer?
>>
> Yep he should
On Wed, 31 Oct 2012 11:57:49 -0300
Alexis Ballier wrote:
> On Tue, 30 Oct 2012 21:18:02 +0100
> Michał Górny wrote:
> [...]
> > Don't even try to touch any of my eclasses without prior asking.
>
> A bit aggressive but its rather obvious that this is the norm not the
> exception, meaning the arg
On Tue, 30 Oct 2012 23:22:01 +0200
Samuli Suominen wrote:
[...]
> One of the commits was before anything was said to ML (the EAPI
> change), the comment was later but the commenter didn't notice it
> just got fixed minutes before that.
>
> I didn't ignore anything, but pointed this thread and the
On Tue, 30 Oct 2012 21:18:02 +0100
Michał Górny wrote:
[...]
> Don't even try to touch any of my eclasses without prior asking.
A bit aggressive but its rather obvious that this is the norm not the
exception, meaning the argument 'I do not want to diverge from
$other eclass' is moot.
On Wed, Oct 31, 2012 at 9:18 AM, wrote:
> Maybe you should remember that non-devs simply /aren't allowed/ to
> assign bugs correctly...
>
> And if you look closer into these bugs, you might discover that jer
> instructed this guy to file separate bugs. (see #440178)
>
Fair points, and clearly th
29.10.2012 18:39, Rich Freeman wrote:
> On Mon, Oct 29, 2012 at 10:13 AM, Rick "Zero_Chaos" Farina
>> but would anyone be interested in blocking using lbzip2
>> by default? It seems pretty safe and I've done dozens of full system
>> builds etc.
>
> Why not just make it an option to start, adverti
31.10.2012 16:39, Michael Palimaka пишет:
> Hi all,
>
> In bug #304435[1], hwoarang suggested merging the devrel handbook[2]
> into the devmanual[3].
>
> As the project has grown, so has the amount - and dispersion - of
> development information. I believe consolidation of this information
> into a
This may help a few test suites and shouldn't hurt much of the others
(which weren't broken already).
Done only for out-of-source builds as that's where we control the build
directories.
---
gx86/eclass/distutils-r1.eclass | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff -
Some of the packages want to access that directory (lxml for example),
and they have to do globbing to guess the suffix. Since we use
per-implementation build dirs anyway, let's just use a simple '/lib'
there.
I'm doing this for out-of-source builds only since we don't set
--build-base for in-sour
Maybe you should remember that non-devs simply /aren't allowed/ to
assign bugs correctly...
And if you look closer into these bugs, you might discover that jer
instructed this guy to file separate bugs. (see #440178)
aranea
signature.asc
Description: PGP signature
The php herd is the maintainer, so you should php-b...@gentoo.org (the
herd-to-email mapping can probably be found elsewhere).
Still, please get more of a feeling for how the Portage tree is put
together before doing more automated bug filing, please.
Cheers,
Dirkjan
On Wed, Oct 31, 2012 at 2:0
On Wed, Oct 31, 2012 at 8:31 AM, Dirkjan Ochtman wrote:
>
> If you're going to file bugs "in a semi-automated manner", might as
> well try to assign to the correct maintainer?
How about a policy - no automated bugs may be logged to the bug
wranglers without their prior approval/review.
I wouldn'
2012/10/31 Dirkjan Ochtman :
> That's rather unsurprising...
>
> If you're going to file bugs "in a semi-automated manner", might as
> well try to assign to the correct maintainer?
>
Yep he should've assign them, but anyway the annoying elog messages
are an issue. And quite few packages suffer from
Simply look at the metadata.xml files which can be found in each
package directory.
Though if you don't know these kinds of basics, I'm not sure you
should be doing *any* (semi- or not) automated bug filing.
Cheers,
Dirkjan
On Wed, Oct 31, 2012 at 1:34 PM, Marco Poletti wrote:
> On mer 31 ott
Hi all,
In bug #304435[1], hwoarang suggested merging the devrel handbook[2]
into the devmanual[3].
As the project has grown, so has the amount - and dispersion - of
development information. I believe consolidation of this information
into a single point will make everyone's (especially new
On 31-10-2012 09:51:51 +0200, Samuli Suominen wrote:
> I don't do prefix and I'm _always_ expecting a patch from prefix@ for
> prefix issues.
In that case, please don't invent prefix things yourself. Thanks.
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: Digital si
On 31/10/12 09:50, Fabian Groffen wrote:
On 30-10-2012 23:22:01 +0200, Samuli Suominen wrote:
So exactly what is (your) problem with the current eclass now?
Your eclass pretends to support Prefix, but it is broken in that
respect, and because some other eclass does it the same way (your
claim)
On 31/10/12 03:03, Diego Elio Pettenò wrote:
On 30/10/2012 17:49, Ryan Hill wrote:
And I had to argue to get 1.48 fixed. I'm not sure why we have to keep so
many unbuildable versions in the tree.
Because as mgorny explained earlier he's expecting some fairy to make it
possible to _always_ ins
On 30-10-2012 23:22:01 +0200, Samuli Suominen wrote:
> So exactly what is (your) problem with the current eclass now?
Your eclass pretends to support Prefix, but it is broken in that
respect, and because some other eclass does it the same way (your
claim), you refuse to fix it.
--
Fabian Groffe
57 matches
Mail list logo
