On śro, 2017-06-07 at 11:56 +0200, Alexis Ballier wrote:
> On Wed, 07 Jun 2017 11:27:59 +0200
> Michał Górny wrote:
>
> > On śro, 2017-06-07 at 10:17 +0200, Alexis Ballier wrote:
> > > > Also, do I presume correctly that for all supported cases (i.e.
> > > > those which your nsolve does not rejec
Jason A. Donenfeld schrieb:
RIP acroread.
The only PDF reader on linux that can properly parse PDF Reference XObjects.
Thou shall be missed.
I found the Chrome PDF reader (pdfium) to be a somewhat adequate
replacement. pdfium recently gained the ability to deal with XFA forms,
which are un
On Fri, 09 Jun 2017 11:19:20 +0200
Michał Górny wrote:
> On śro, 2017-06-07 at 11:56 +0200, Alexis Ballier wrote:
> > On Wed, 07 Jun 2017 11:27:59 +0200
> > Michał Górny wrote:
> >
> > > On śro, 2017-06-07 at 10:17 +0200, Alexis Ballier wrote:
> > > > > Also, do I presume correctly that for
On Mon, May 29, 2017 at 5:33 PM, Michał Górny wrote:
>
> Secondly, it might be reasonable to provide configurable priorities for
> solving multi-flag constraints. For example, we could use rightmost-
> preferred logic for package.use, e.g.:
>
> */* PROVIDER_SSL: openssl gnutls
> dev-u
On pią, 2017-06-09 at 14:35 +0200, Jason A. Donenfeld wrote:
> On Mon, May 29, 2017 at 5:33 PM, Michał Górny wrote:
> >
> > Secondly, it might be reasonable to provide configurable priorities for
> > solving multi-flag constraints. For example, we could use rightmost-
> > preferred logic for pack
On pią, 2017-06-09 at 13:41 +0200, Alexis Ballier wrote:
> On Fri, 09 Jun 2017 11:19:20 +0200
> Michał Górny wrote:
>
> > On śro, 2017-06-07 at 11:56 +0200, Alexis Ballier wrote:
> > > On Wed, 07 Jun 2017 11:27:59 +0200
> > > Michał Górny wrote:
> > >
> > > > On śro, 2017-06-07 at 10:17 +0200
On Fri, 09 Jun 2017 14:54:07 +0200
Michał Górny wrote:
> On pią, 2017-06-09 at 13:41 +0200, Alexis Ballier wrote:
> > On Fri, 09 Jun 2017 11:19:20 +0200
> > Michał Górny wrote:
> >
> > > On śro, 2017-06-07 at 11:56 +0200, Alexis Ballier wrote:
> > > > On Wed, 07 Jun 2017 11:27:59 +0200
> >
(cut off the parts where I agree and there's nothing to add)
On pią, 2017-06-09 at 16:16 +0200, Alexis Ballier wrote:
> [...]
> > > In your example above, we'd call 'nsolve("|| ( X )")' and
> > > 'nsolve("|| ( Y )")' (or even simpler, depending on how simplify()
> > > is defined). If both X and Y
Hi, everyone.
As you may or may not know, PMS says rather little about REQUIRED_USE
[1,2]. The largest past of the definition is shared with other
dependency-like specifications [3].
Similarly to regular dependency specifications, PMS is rather lax in
nesting things. While this isn't a major prob
