Re: build profile syntax ideas
- To: firstname.lastname@example.org, Wookey <email@example.com>
- Subject: Re: build profile syntax ideas
- From: "Johannes Schauer" <firstname.lastname@example.org>
- Date: Thu, 06 Feb 2014 18:52:36 +0100
- Message-id: <[🔎] 20140206175236.3663.39050@hoothoot>
- Mail-followup-to: email@example.com, Wookey <firstname.lastname@example.org>,
- In-reply-to: <20131204134738.2752.60436@hoothoot>
- References: <20130419194252.17205.76995@hoothoot> <20130422221407.3500.52444@hoothoot> <CAAZ6_fAQSHx6yeWT2QZQ9xeJjJcQzyB5UMt18XHRWFemail@example.com> <20130518081311.25446.78664@hoothoot> <20130816015945.GC24714@stoneboat.aleph1.co.uk> <20130816121504.GB20673@gaara.hadrons.org> <20130917103117.2726.40546@hoothoot> <20131021053123.GA20313@gaara.hadrons.org> <20131204074815.GB21007@gaara.hadrons.org> <20131204134738.2752.60436@hoothoot>
Quoting Johannes Schauer (2013-12-04 14:47:38)
> > I've also changed the restrictions logic to match the arch one, because the
> > one proposed here didn't make sense to me in some cases,
> I spent quite some time on it because it's indeed quite confusing.
again two months passed.
Could you share your thoughts to the situation with mixed positive and negative
As I lined out in my last email, the fact that you didnt understand how it was
supposed to work (at least in my head) even though I supplied working unit
tests (which you changed according to your interpretation), might just mean
that they are too complex and confusing to be worth it right now.
What do you think?
We would like to send patches to more tools (like apt) but before that we'd
like to have a clear decision on this issue.
Thanks a lot!