-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/10/15 05:39 AM, hasufell wrote:
> On 10/13/2015 09:51 AM, Alexis Ballier wrote:
>>
>> that would work too, but dtd provides standardization, and
>> avoids duplicating package-wide information (meaning of
>> slot/subslot) in every single ebuild
On 13.10.2015 11:39, hasufell wrote:
> On 10/13/2015 09:51 AM, Alexis Ballier wrote:
>>
>> that would work too, but dtd provides standardization, and avoids
>> duplicating package-wide information (meaning of slot/subslot) in every
>> single ebuild.
>>
>
> Yeah, the only thing that I wasn't sure a
On Tue, 13 Oct 2015 11:39:04 +0200
hasufell wrote:
> On 10/13/2015 09:51 AM, Alexis Ballier wrote:
> >
> > that would work too, but dtd provides standardization, and avoids
> > duplicating package-wide information (meaning of slot/subslot) in
> > every single ebuild.
> >
>
> Yeah, the only t
On 10/13/2015 09:51 AM, Alexis Ballier wrote:
>
> that would work too, but dtd provides standardization, and avoids
> duplicating package-wide information (meaning of slot/subslot) in every
> single ebuild.
>
Yeah, the only thing that I wasn't sure about is the subslots part. With
the proposed p
On Tue, 13 Oct 2015 08:11:44 +0800
Ian Delaney wrote:
> On Mon, 12 Oct 2015 20:01:15 +0200
> hasufell wrote:
>
> > On 10/12/2015 07:49 PM, Alexis Ballier wrote:
> > > On Mon, 12 Oct 2015 19:19:33 +0200
> > > Julian Ospald wrote:
> > >
> > >> There seems to be some general confusion about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 12 Oct 2015 23:49:11 +0200
"Andreas K. Huettel" wrote:
> There seems to be some general confusion about specific package SLOTs
> and their meaning, since there can be several naming schemes applied
> and documentation is either non-existent
On Mon, 12 Oct 2015 20:01:15 +0200
hasufell wrote:
> On 10/12/2015 07:49 PM, Alexis Ballier wrote:
> > On Mon, 12 Oct 2015 19:19:33 +0200
> > Julian Ospald wrote:
> >
> >> There seems to be some general confusion about specific package
> >> SLOTs and their meaning, since there can be several na
Am Montag, 12. Oktober 2015, 19:19:33 schrieb Julian Ospald:
> An example use case for media-libs/libpng would be:
>
> For building against. This is the only slot
> that provides headers and command line tools.
> For binary compatibility, provides
> libpng12.so.0. For binary compat
On Mon, 12 Oct 2015 20:01:15 +0200
hasufell wrote:
> On 10/12/2015 07:49 PM, Alexis Ballier wrote:
> > On Mon, 12 Oct 2015 19:19:33 +0200
> > Julian Ospald wrote:
> >
> >> There seems to be some general confusion about specific package
> >> SLOTs and their meaning, since there can be several
On 10/12/2015 07:49 PM, Alexis Ballier wrote:
> On Mon, 12 Oct 2015 19:19:33 +0200
> Julian Ospald wrote:
>
>> There seems to be some general confusion about specific package SLOTs
>> and their meaning, since there can be several naming schemes applied
>> and documentation is either non-existent
On Mon, 12 Oct 2015 19:19:33 +0200
Julian Ospald wrote:
> There seems to be some general confusion about specific package SLOTs
> and their meaning, since there can be several naming schemes applied
> and documentation is either non-existent or is inside the ebuild via
> comments.
> Because of th
There seems to be some general confusion about specific package SLOTs
and their meaning, since there can be several naming schemes applied
and documentation is either non-existent or is inside the ebuild via
comments.
Because of that it should be part of metadata.xml.
An example use case for media
12 matches
Mail list logo
