On 9/11/14 12:20 AM, Michał Górny wrote:
> I would like the post-install QA checks to be modularized, standardized
> and extensible. For a start, I've split most of the function into
> install-qa-check.d/ scripts in Portage and made install_qa_check()
> function run them [1]. However, that's just a
Markos Chandras posted on Wed, 10 Sep 2014 21:21:24 +0100 as excerpted:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 09/10/2014 03:01 PM, Tom Wijsman wrote:
>> On Tue, 9 Sep 2014 21:45:49 +0200 Michał Górny
>> wrote:
>>
>>> Let's keep it short: I think herds don't serve any specia
Hello, everyone.
Portage has currently two major QA mechanisms: repoman
and install_qa_check(). While we would love to put all the QA
in repoman and make it the ultimate tool preventing bad commits, it is
very limited in power. Most importantly, it can't really access
the build environment of an e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/10/2014 03:01 PM, Tom Wijsman wrote:
> On Tue, 9 Sep 2014 21:45:49 +0200 Michał Górny
> wrote:
>
>> Let's keep it short: I think herds don't serve any special
>> purpose nowadays. Their existence is mostly resulting in lack of
>> consistency
# Ulrich Müller (10 Sep 2014)
# Multiple security vulnerabilities, bug #510960.
# Masked for removal in 30 days, bug #517932.
app-emulation/emul-linux-x86-compat
pgpLYsx1bHQzD.pgp
Description: PGP signature
On Wed, Sep 10, 2014 at 10:18 AM, Michał Górny wrote:
> Dnia 2014-09-10, o godz. 07:53:31
> Rich Freeman napisał(a):
>
>> On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos wrote:
>> >
>> > Personally I would vote for simply have a tag pointing to
>> > the alias but we would still need to keep a list
On Sun, Sep 07, 2014 at 09:03:00PM -0400, Rich Freeman wrote:
> Right now the general policy is that we don't allow unmasked (hard or
> via keywords) ebuilds in the tree if they use an scm to fetch their
> sources. There are a bunch of reasons for this, and for the most part
> they make sense.
>
On Wed, Sep 10, 2014 at 07:53:31AM -0400, Rich Freeman wrote:
> On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos wrote:
> >
> > Personally I would vote for simply have a tag pointing to
> > the alias but we would still need to keep a list of real maintainers for
> > that alias as usually not all peop
Tom Wijsman:
>> It improves usability by providing additional information.
>
> Usability is not to be found in information that is subject to change.
>
Please also set DEPEND, RDEPEND, EGIT_REPO_URI, DESCRIPTION and the rest
of them to "", because they are all subject to change.
> So, both quot
On Wed, 10 Sep 2014 13:56:04 +
hasufell wrote:
> Tom Wijsman:
> > On Tue, 09 Sep 2014 19:12:28 +
> > hasufell wrote:
> >
> >> Jauhien Piatlicki:
> >>>
> >>> When I accept ~arch I expect that no live ebuilds will be built. I
> >>> think other gentoo users expect the same.
> >>
> >> Just
Hi,
On Wed, 10 Sep 2014 07:50:05 +0200 J. Roeleveld wrote:
> > I'm talking about the following research:
> > https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact
> > =8&ved=0CB4QFjAA&url=https%3A%2F%2Fwww.blackhat.com%2Fpresentations%2Fbh-eur
> > ope-06%2Fbh-eu-06-biondi%2F
Dnia 2014-09-10, o godz. 07:53:31
Rich Freeman napisał(a):
> On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos wrote:
> >
> > Personally I would vote for simply have a tag pointing to
> > the alias but we would still need to keep a list of real maintainers for
> > that alias as usually not all peopl
On Tue, 9 Sep 2014 21:45:49 +0200
Michał Górny wrote:
> Let's keep it short: I think herds don't serve any special purpose
> nowadays. Their existence is mostly resulting in lack of consistency
> and inconveniences.
+1; to summarize my thoughts: Herds misrepresent manpower.
Tom Wijsman:
> On Tue, 09 Sep 2014 19:12:28 +
> hasufell wrote:
>
>> Jauhien Piatlicki:
>>>
>>> When I accept ~arch I expect that no live ebuilds will be built. I
>>> think other gentoo users expect the same.
>>
>> Just because users are used to it doesn't make it better.
>
> How does it "ma
On Tue, 09 Sep 2014 19:12:28 +
hasufell wrote:
> Jauhien Piatlicki:
> >
> > When I accept ~arch I expect that no live ebuilds will be built. I
> > think other gentoo users expect the same.
>
> Just because users are used to it doesn't make it better.
How does it "make it better" for users
On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos wrote:
>
> Personally I would vote for simply have a tag pointing to
> the alias but we would still need to keep a list of real maintainers for
> that alias as usually not all people listed in the alias are willing to
> maintain the packages.
>
I thin
On Tue, Sep 9, 2014 at 6:54 PM, Kent Fredric wrote:
>
> On 10 September 2014 10:23, Michał Górny wrote:
>>
>> I don't understand your concern. I'm only saying we should stop relying
>> on that stupid out-of-repository herds.xml file and put the e-mail
>> address directly in metadata.xml. Bugzilla
El mar, 09-09-2014 a las 21:45 +0200, Michał Górny escribió:
[...]
> I believe it would be benfiicial to just deprecate and eventually drop
> in favor of explicit using the alias. I don't know
> if someone has other use of herds.xml but it the contents are either
> outdated or redundant. Therefor
On Wed, Sep 10, 2014 at 4:08 AM, J. Roeleveld wrote:
>
> But on slower machines, as I am used to fast ones, I tend to notice the lack
> of parallellism during the emerge-phase.
>
Diego used to point out that lack of parallelism was always a
challenge with running a tinderbox. You can have 32 cor
J. Roeleveld posted on Wed, 10 Sep 2014 10:08:56 +0200 as excerpted:
>> The vi and emacs camps agreeing on something? Impossible!
>
> I think both camps do the following:
> emerge
> emerge -C nano as one of the first steps.
>
> The first thing I do on a new install as soon as a portage tree is
On Sunday, September 07, 2014 05:57:57 PM Joshua Kinard wrote:
> On 09/07/2014 17:04, Rich Freeman wrote:
> > On Sun, Sep 7, 2014 at 4:33 PM, Joshua Kinard
wrote:
> >> As for Parallel builds, do you make make -jX? Or running concurrent
> >> emerges in different shells? I wasn't commenting a
21 matches
Mail list logo
