Mail archive
alpine-aports

Re: [alpine-aports] [PATCH] testing/lablgtk: new aport

From: Leonardo Arena <rnalrd_at_gmail.com>
Date: Fri, 27 Jan 2017 14:35:43 +0100

On mer, 2017-01-25 at 14:25 +0100, Jean-Louis Fuchs wrote:
> Hi |_eo
>
> On Wed, Jan 25, 2017 at 01:46:02PM +0100, Leonardo Arena wrote:
>
> I'm not familiar with ocaml, except for building unison.
>
> >
> > The dev stuff is ~5 MB, half of the package size (10MB).
> > I'm not familiar with ocaml. What would be the inconvenience in
> > having
> > a separate -dev pkg?
> If you do a native install you need lablgtk and lablgtk-dev. I
> thought
> it might lead to confusion. I think we have these options:
>
> 1. Have the dev split and develeopers just have to remember
> installing
>    both packages if they want to do a native-compile.
>
> 2. Add lablgtk to depends_dev, so if you intend to do a native-
> compile
>    you will automatically get lablgtk.
>
> 3. My current solution.
>
> I first wanted to go for 2. And then thought it might be considered a
> hack.
>
> >
> > Would a user just want to use it at run-time only
> > or it's an unlikely scenario?
> I guess a user never wants run-time only, since the distribution
> usually does a native-compile. For example the native-compile package
> of unison doesn't need lablgtk at run-time since its all linked into
> unison.
>
> But a ocaml developer probably wants run-time only, because he is
> using the interpreter during development.
>
> >
> > From Alpine packaging perspective only, 5 MB less in the system are
> > definitely worthy a pkg separation.
> So I guess we have to go for 1. or 2. let me know if 2. is ok.
>

Solution 2 sounds good to me.

I'm merged this patch and unison with this modification.

Thanks!

|_eo





---
Unsubscribe:  alpine-aports+unsubscribe_at_lists.alpinelinux.org
Help:         alpine-aports+help_at_lists.alpinelinux.org
---
Received on Fri Jan 27 2017 - 14:35:43 GMT