On Thu, 2011-04-21 at 17:18 +0200, Julien Danjou wrote:
> On Thu, Apr 21 2011, Jamey Sharp wrote:
>
> > - In libxcb master, I'd be happy to change configure.ac to default to
> > not building xprint. I'd personally continue building it because I
> > build all known extensions, just to check for
On Thu, Apr 21 2011, Jamey Sharp wrote:
> - In libxcb master, I'd be happy to change configure.ac to default to
> not building xprint. I'd personally continue building it because I
> build all known extensions, just to check for build regressions, but
> there's no reason everybody else needs
On Thu, Apr 21, 2011 at 04:22:17PM +0200, Julien Danjou wrote:
> On Thu, Apr 21 2011, Drew Parsons wrote:
> > cc: xcb maintainers: should you keep libxcb-xprint0 ? Do we need to talk
> > about this? libxcb-xprint0 has no relation (in a packaging sense) to
> > xprint.
>
> I see no harm providing it
On Thu, Apr 21 2011, Drew Parsons wrote:
> cc: xcb maintainers: should you keep libxcb-xprint0 ? Do we need to talk
> about this? libxcb-xprint0 has no relation (in a packaging sense) to
> xprint.
I see no harm providing it. It exists, so we can just let it be. Nothing
depends on it I guess, and
4 matches
Mail list logo
