On Tue, 2014-08-19 at 12:41 +0200, Koen Kooi wrote:
> Op 18 aug. 2014, om 17:35 heeft Richard Purdie
> het volgende geschreven:
>
> > On Mon, 2014-08-18 at 15:39 +0100, Richard Purdie wrote:
> >> On Mon, 2014-08-18 at 15:14 +0200, Martin Jansa wrote:
> >>> Well then maybe that allarch package wi
Op 18 aug. 2014, om 17:35 heeft Richard Purdie
het volgende geschreven:
> On Mon, 2014-08-18 at 15:39 +0100, Richard Purdie wrote:
>> On Mon, 2014-08-18 at 15:14 +0200, Martin Jansa wrote:
>>> Well then maybe that allarch package with perl dependency shouldn't be
>>> marked as allarch.
>>
>> T
On Mon, 2014-08-18 at 15:39 +0100, Richard Purdie wrote:
> On Mon, 2014-08-18 at 15:14 +0200, Martin Jansa wrote:
> > Well then maybe that allarch package with perl dependency shouldn't be
> > marked as allarch.
>
> Take a step back and think about this from the end user system
> perspective. The
On Mon, 2014-08-18 at 15:14 +0200, Martin Jansa wrote:
> On Mon, Aug 18, 2014 at 01:46:50PM +0100, Richard Purdie wrote:
> > As some people are already painfully aware, the current way packagegroup
> > and allarch interact with the sstate signatures is painful.
> >
> > Some example problem cases:
On Mon, Aug 18, 2014 at 09:42:50PM +0800, Robert Yang wrote:
>
>
> On 08/18/2014 09:14 PM, Martin Jansa wrote:
> > On Mon, Aug 18, 2014 at 01:46:50PM +0100, Richard Purdie wrote:
> >> As some people are already painfully aware, the current way packagegroup
> >> and allarch interact with the sstat
On 08/18/2014 09:14 PM, Martin Jansa wrote:
On Mon, Aug 18, 2014 at 01:46:50PM +0100, Richard Purdie wrote:
As some people are already painfully aware, the current way packagegroup
and allarch interact with the sstate signatures is painful.
Some example problem cases:
* An allarch package of
On Mon, Aug 18, 2014 at 01:46:50PM +0100, Richard Purdie wrote:
> As some people are already painfully aware, the current way packagegroup
> and allarch interact with the sstate signatures is painful.
>
> Some example problem cases:
>
> * An allarch package of scripts with an interpretor dependen
As some people are already painfully aware, the current way packagegroup
and allarch interact with the sstate signatures is painful.
Some example problem cases:
* An allarch package of scripts with an interpretor dependency (e.g perl)
* A packagegroup with dependencies on something which is debi