Fabian Groffen posted on Wed, 26 Oct 2011 23:00:22 +0200 as excerpted:
> On 26-10-2011 14:02:12 -0400, Rich Freeman wrote:
>> Well, if the desire to trim changelogs is generally agreed upon we
>> could always just count the lines and post a top-100 list or something
>> and let package maintainers
Ian Stakenvicius posted on Wed, 26 Oct 2011 14:55:45 -0400 as excerpted:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 26/10/11 02:50 PM, William Hubbs wrote:
>> All,
>>
>> openrc has two network stacks currently. The first is the one most
>> people are using afaik, the net.* scrip
Francisco Blas Izquierdo Riera (klondike) wrote:
> El 23/10/11 05:56, Steven J Long escribió:
>> Will we be able to switch off SSP via config, or will we have to setup
>> our own profile?
> This should do the trick:
> CFLAGS=$CFLAGS -fno-stack-protector
Well, with quotes ;) but yeah that's what I
On Wed, 26 Oct 2011 19:33:56 +0200
Bruno wrote:
> Is there some guideline about old entries in the ChangeLog?
>
> Over the past months ChangeLogs represent a big part of the tree, some
> of them being pretty big and going back many changes (hundreds of them)
> and years (even for actively mainta
i can't see any ebuild/eclass using egethome, egetshell,
is-login-disabled from portability.eclass. anyone have a reason for
keeping these before i punt them ?
-mike
hopefully i didn't break anything before i go to sleep ;D
http://sources.gentoo.org/eclass/toolchain.eclass?r1=1.474&r2=1.475
http://sources.gentoo.org/eclass/eutils.eclass?r1=1.366&r2=1.367
-mike
El mié, 26-10-2011 a las 22:58 +0200, Fabian Groffen escribió:
> On 26-10-2011 20:05:05 +0200, Pacho Ramos wrote:
> > Why don't we try to reach a consensus? Maybe we should be allowed to
> > simply run echangelog (or whatever is used) to generate a message like:
> > 26 Oct 2011; Pacho Ramos -pan
Fabian Groffen schrieb:
> You can see it has been removed, but you typically want to know why.
> That's the idea of the ChangeLog file.
One of the arguments for logging everything in ChangeLog was that
extracting this kind information from CVS can be cumbersome. So, I would
not agree with "typical
On 26-10-2011 14:02:12 -0400, Rich Freeman wrote:
> Well, if the desire to trim changelogs is generally agreed upon we
> could always just count the lines and post a top-100 list or something
> and let package maintainers go in and truncate things as seems bet to
> them, with the guideline to keep
On 26-10-2011 20:05:05 +0200, Pacho Ramos wrote:
> Why don't we try to reach a consensus? Maybe we should be allowed to
> simply run echangelog (or whatever is used) to generate a message like:
> 26 Oct 2011; Pacho Ramos -pangomm-2.26.3.ebuild
>
> And simply that
>
> Pros:
> - People refusing
i'm indifferent to the newnet status
-mike
On Wed, 26 October 2011 Pacho Ramos wrote:
> El mié, 26-10-2011 a las 19:33 +0200, Bruno escribió:
> > On Wed, 26 October 2011 Fabian Groffen wrote:
> > > However, this also allows to do all kinds of other actions to the
> > > ChangeLog file, without actually adding an entry for the current chang
On Wed, Oct 26, 2011 at 2:05 PM, Pacho Ramos wrote:
> El mié, 26-10-2011 a las 19:15 +0200, Fabian Groffen escribió:
>> On 26-10-2011 19:11:24 +0200, Michał Górny wrote:
>> > On Wed, 26 Oct 2011 19:06:07 +0200
>> > Fabian Groffen wrote:
>> >
>> > > > 3) one step towards preventing useless ChangeL
> On Wed, 26 Oct 2011, Andreas K Huettel wrote:
> 1) Why is there no ChangeLog in the eclass directory?
> In my personal opinion this is missing there, if only for historical
> reasons... Should we still start one?
It's never too late. Even echangelog works in the eclass directory,
once you
> > As for codifying this, applying software to automate splitting
> > changelogs in this manner could be initially challenging as I've seen
> > a few Changelogs with really inconsistent style at the bottom of them.
>
> How many really long changelogs do we have now? Maybe we should just
> split t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/10/11 02:50 PM, William Hubbs wrote:
> All,
>
> openrc has two network stacks currently. The first is the one most
> people are using afaik, the net.* scripts, which I will call oldnet in
> the rest of this message.
>
> The second is the net
All,
openrc has two network stacks currently. The first is the one most
people are using afaik, the net.* scripts, which I will call oldnet in
the rest of this message.
The second is the network and staticroute scripts, which we do not use
or support in gentoo, primarily because it does not all
On Thu, 27 Oct 2011 07:00:36 +1300
Kent Fredric wrote:
> On 27 October 2011 06:46, Andreas K. Huettel
> wrote:
>
> >
> > 2) I'd like to suggest that for changelogs that grow beyond a
> > certain size (e.g. profiles/ChangeLog)
> > the file is "rotated" similar to /var/log logfiles. I.e. the
> >
On 10/26/2011 08:46 PM, Andreas K. Huettel wrote:
> Dear all,
>
> two small suggestions regarding ChangeLogs:
>
> 1) Why is there no ChangeLog in the eclass directory?
> In my personal opinion this is missing there, if only for historical
> reasons... Should we still start one?
>
> 2) I'd lik
El mié, 26-10-2011 a las 19:46 +0200, Andreas K. Huettel escribió:
> Dear all,
>
> two small suggestions regarding ChangeLogs:
>
> 1) Why is there no ChangeLog in the eclass directory?
> In my personal opinion this is missing there, if only for historical
> reasons... Should we still start one
El mié, 26-10-2011 a las 19:33 +0200, Bruno escribió:
> On Wed, 26 October 2011 Fabian Groffen wrote:
> > However, this also allows to do all kinds of other actions to the
> > ChangeLog file, without actually adding an entry for the current change
> > being committed, as we've already seen in prac
El mié, 26-10-2011 a las 19:15 +0200, Fabian Groffen escribió:
> On 26-10-2011 19:11:24 +0200, Michał Górny wrote:
> > On Wed, 26 Oct 2011 19:06:07 +0200
> > Fabian Groffen wrote:
> >
> > > > 3) one step towards preventing useless ChangeLog entries.
> > >
> > > Also this has been discussed and d
On Wed, Oct 26, 2011 at 1:56 PM, Kent Fredric wrote:
> On 27 October 2011 06:33, Bruno wrote:
>>
>> Is there some guideline about old entries in the ChangeLog?
>>
>> Over the past months ChangeLogs represent a big part of the tree, some
>> of them being pretty big and going back many changes (hun
On 27 October 2011 06:46, Andreas K. Huettel wrote:
>
> 2) I'd like to suggest that for changelogs that grow beyond a certain size
> (e.g. profiles/ChangeLog)
> the file is "rotated" similar to /var/log logfiles. I.e. the current file
> is renamed with a date extension and a
> new file is started
On 27 October 2011 06:33, Bruno wrote:
>
> Is there some guideline about old entries in the ChangeLog?
>
> Over the past months ChangeLogs represent a big part of the tree, some
> of them being pretty big and going back many changes (hundreds of them)
> and years (even for actively maintained ebu
Dear all,
two small suggestions regarding ChangeLogs:
1) Why is there no ChangeLog in the eclass directory?
In my personal opinion this is missing there, if only for historical reasons...
Should we still start one?
2) I'd like to suggest that for changelogs that grow beyond a certain size
(e
On Wed, 26 October 2011 Fabian Groffen wrote:
> However, this also allows to do all kinds of other actions to the
> ChangeLog file, without actually adding an entry for the current change
> being committed, as we've already seen in practice.
> The Council would like to remind developers that it is
On 26-10-2011 19:11:24 +0200, Michał Górny wrote:
> On Wed, 26 Oct 2011 19:06:07 +0200
> Fabian Groffen wrote:
>
> > > 3) one step towards preventing useless ChangeLog entries.
> >
> > Also this has been discussed and decided upon by the current and
> > previous Councils, so also that opinion is
On Wed, 26 Oct 2011 19:06:07 +0200
Fabian Groffen wrote:
> > 3) one step towards preventing useless ChangeLog entries.
>
> Also this has been discussed and decided upon by the current and
> previous Councils, so also that opinion is unlikely to suddenly
> change.
I meant the useless ChangeLog m
On 26-10-2011 18:49:27 +0200, Michał Górny wrote:
> > Ok, what's your rationale behind that?
>
> 1) easier migration to autogenerated ChangeLogs if we want that at
> some point,
Since the Council has discussed that for several meetings to reach a
discussion, I don't think they are shortly going t
All,
As decided by the Council in its last meeting at the beginning of this
month, ChangeLogs will not be generated from VCS commit messages,
because the Council wants to keep the ability to edit generated
ChangeLog messages [1].
As a result, the Council took this up with the Portage team, to mak
On Wed, 26 Oct 2011 18:37:24 +0200
Fabian Groffen wrote:
> On 26-10-2011 18:35:51 +0200, Michał Górny wrote:
> > On Wed, 26 Oct 2011 18:30:25 +0200
> > Fabian Groffen wrote:
> >
> > > In less than two weeks, the council will meet again. This is the
> > > time to raise and prepare items that th
On 26-10-2011 18:35:51 +0200, Michał Górny wrote:
> On Wed, 26 Oct 2011 18:30:25 +0200
> Fabian Groffen wrote:
>
> > In less than two weeks, the council will meet again. This is the time
> > to raise and prepare items that the council should put on the agenda
> > to vote on.
>
> As an extension
On Wed, 26 Oct 2011 18:30:25 +0200
Fabian Groffen wrote:
> In less than two weeks, the council will meet again. This is the time
> to raise and prepare items that the council should put on the agenda
> to vote on.
As an extension of ChangeLog topic, I'd like to suggest to require
developers to
All,
In less than two weeks, the council will meet again. This is the time
to raise and prepare items that the council should put on the agenda to
vote on.
Please respond to this email with agenda items. Please do not hestitate
to repeat your agenda item here with a pointer if you previously
su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/10/11 10:20 AM, "Paweł Hajdan, Jr." wrote:
> I was browsing toolchain.eclass and noticed this:
>
> if [[ ${PN} != "kgcc64" && ${PN} != gcc-* ]] ; then
> ...
> [[ -n ${SPECS_VER} ]] && IUSE+=" nossp"
> ...
>
> if tc_version_is_
I was browsing toolchain.eclass and noticed this:
if [[ ${PN} != "kgcc64" && ${PN} != gcc-* ]] ; then
...
[[ -n ${SPECS_VER} ]] && IUSE+=" nossp"
...
if tc_version_is_at_least 3 ; then
...
if tc_version_is_at_least "4.4" ; then
IUSE+=" graphite"
On 10/25/11 3:58 PM, Anthony G. Basile wrote:
> Zorry's the expert here, so I'll ask him to correct me if I miss
> anything or get something wrong.
>
> You won't get hardening without those patches. So they need to be there
> if the user switches specs from vanilla to hardened.
Thanks, I've file
38 matches
Mail list logo
