On Mon, 4 Jul 2022 22:49:25 -0400
Ionen Wolkens wrote:
On Mon, Jul 04, 2022 at 04:19:12PM +0200, Florian Schmaus wrote:
> I'd like to propose a new metadata XML element for packages:
>
>
>
> Maintainers can signal to other developers (and of course contributors
> in general) that they are
> On 5 Jul 2022, at 00:21, Robin H. Johnson wrote:
>
> On Mon, Jul 04, 2022 at 05:27:03PM +0200, David Seifert wrote:
>> On Mon, 2022-07-04 at 16:19 +0200, Florian Schmaus wrote:
>>> I'd like to propose a new metadata XML element for packages:
>>>
>>>
> ...
>> Ultimately, all these thing
> On 5 Jul 2022, at 03:49, Ionen Wolkens wrote:
>
> On Mon, Jul 04, 2022 at 04:19:12PM +0200, Florian Schmaus wrote:
>> I'd like to propose a new metadata XML element for packages:
>>
>>
>>
>> Maintainers can signal to other developers (and of course contributors
>> in general) that they are
> On 5 Jul 2022, at 04:24, Ionen Wolkens wrote:
>
> On Mon, Jul 04, 2022 at 10:53:41PM -0400, Ionen Wolkens wrote:
>> On Mon, Jul 04, 2022 at 10:49:25PM -0400, Ionen Wolkens wrote:
>>> On Mon, Jul 04, 2022 at 04:19:12PM +0200, Florian Schmaus wrote:
I'd like to propose a new metadata XML e
On Mon, Jul 04, 2022 at 10:53:41PM -0400, Ionen Wolkens wrote:
> On Mon, Jul 04, 2022 at 10:49:25PM -0400, Ionen Wolkens wrote:
> > On Mon, Jul 04, 2022 at 04:19:12PM +0200, Florian Schmaus wrote:
> > > I'd like to propose a new metadata XML element for packages:
> > >
> > >
> > >
> > > Mai
On Mon, Jul 04, 2022 at 10:49:25PM -0400, Ionen Wolkens wrote:
> On Mon, Jul 04, 2022 at 04:19:12PM +0200, Florian Schmaus wrote:
> > I'd like to propose a new metadata XML element for packages:
> >
> >
> >
> > Maintainers can signal to other developers (and of course contributors
> > in g
On Mon, Jul 04, 2022 at 04:19:12PM +0200, Florian Schmaus wrote:
> I'd like to propose a new metadata XML element for packages:
>
>
>
> Maintainers can signal to other developers (and of course contributors
> in general) that they are happy with others to make changes to the
> ebuilds wit
> On 5 Jul 2022, at 00:49, Rich Freeman wrote:
>
> On Mon, Jul 4, 2022 at 7:21 PM Robin H. Johnson wrote:
>>
>> It had 3 states however:
>> a) go ahead and touch it, no additional approvals needed
>> b) please get a maintainer to approve it
>> c) do not touch it
>>
>
> ++
>
> Though to be
On Mon, Jul 4, 2022 at 7:21 PM Robin H. Johnson wrote:
>
> It had 3 states however:
> a) go ahead and touch it, no additional approvals needed
> b) please get a maintainer to approve it
> c) do not touch it
>
++
Though to be fair b is really no different from what just about
anybody can do via a
On Mon, Jul 04, 2022 at 05:27:03PM +0200, David Seifert wrote:
> On Mon, 2022-07-04 at 16:19 +0200, Florian Schmaus wrote:
> > I'd like to propose a new metadata XML element for packages:
> >
> >
...
> Ultimately, all these things really matter when only the defaults
> change. Turn-right-on-
On Mon, 2022-07-04 at 16:19 +0200, Florian Schmaus wrote:
> I'd like to propose a new metadata XML element for packages:
>
>
>
> Maintainers can signal to other developers (and of course contributors
> in general) that they are happy with others to make changes to the
> ebuilds without pri
I'd like to propose a new metadata XML element for packages:
Maintainers can signal to other developers (and of course contributors
in general) that they are happy with others to make changes to the
ebuilds without prior consultation of the maintainer.
Of course, this is not a free tick
On EAPI 6, or newer, invoke einstalldocs in
java-pkg-simple_src_install.
Closes: https://bugs.gentoo.org/789582
Signed-off-by: Florian Schmaus
---
eclass/java-pkg-simple.eclass | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/eclass/java-pkg-simple.eclass b/eclass/java-
13 matches
Mail list logo
