Reply-To: developer@it-offshore.co.uk
Subject: [alpine-devel] Re: modemmanager-dev and libmm-glib-dev
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: alpine-devel@lists.alpinelinux.org
References: <20170606194343.572d0603@ncopa-desktop.copa.dup.pw>
From: Stuart Cardall <developer@it-offshore.co.uk>
Message-ID: <3b39aa24-8ca9-9ab4-4992-602940b9a154@it-offshore.co.uk>
Date: Wed, 7 Jun 2017 04:04:26 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.1.1
Precedence: list
MIME-Version: 1.0
In-Reply-To: <20170606194343.572d0603@ncopa-desktop.copa.dup.pw>
Content-Type: multipart/alternative;
 boundary="------------F156785A014E5911E3DD6A86"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------F156785A014E5911E3DD6A86
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi,

I've moved the libmm-glib-dev files into modemmanager-dev & changed the
$makedepends in networkmanager & network-manager-applet:

https://github.com/alpinelinux/aports/pull/1624

Stuart.


On 06/06/2017 06:43 PM, Natanael Copa wrote:
> Hi,
>
> I noticed that the modemmanager aport has a separate libmm-glib-dev
> subpackage. I wonder why it needs to be separate from our traditional
> modemmanager-dev?
>
> I know that we for some packages make exception, like libpq and
> libmysql may make sense to have separate -dev package for, but in this
> case it seems that libmm-glib-dev needs to depend on modemmanager-dev:
>
>> ...
>> checking for LIBGEOCLUE... yes
>> checking for ModemManager... no
>> configure: error: Package requirements (mm-glib >= 1.0) were not met:
>>
>> Package 'ModemManager', required by 'mm-glib', not found
>>
>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> installed software in a non-standard prefix.
>>
>> Alternatively, you may set the environment variables ModemManager_CFLAGS
>> and ModemManager_LIBS to avoid the need to call pkg-config.
>> ...
> Can we simply drop the libmm-glib-dev package and put all the
> development files into modemmanager-dev, like we do with the rest of
> our aports?
>
> -nc


--------------F156785A014E5911E3DD6A86
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000099">
    <p><font face="Helvetica, Arial, sans-serif">Hi,</font></p>
    <p><font face="Helvetica, Arial, sans-serif">I've moved the
        libmm-glib-dev files into modemmanager-dev &amp; changed the
        $makedepends in networkmanager &amp; network-manager-applet:</font></p>
    <p><font face="Helvetica, Arial, sans-serif"><a
          moz-do-not-send="true"
          href="https://github.com/alpinelinux/aports/pull/1624">https://github.com/alpinelinux/aports/pull/1624</a><br>
      </font></p>
    <p><font face="Helvetica, Arial, sans-serif">Stuart.</font><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 06/06/2017 06:43 PM, Natanael Copa
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:20170606194343.572d0603@ncopa-desktop.copa.dup.pw">
      <pre wrap="">Hi,

I noticed that the modemmanager aport has a separate libmm-glib-dev
subpackage. I wonder why it needs to be separate from our traditional
modemmanager-dev?

I know that we for some packages make exception, like libpq and
libmysql may make sense to have separate -dev package for, but in this
case it seems that libmm-glib-dev needs to depend on modemmanager-dev:

</pre>
      <blockquote type="cite">
        <pre wrap="">...
checking for LIBGEOCLUE... yes
checking for ModemManager... no
configure: error: Package requirements (mm-glib &gt;= 1.0) were not met:

Package 'ModemManager', required by 'mm-glib', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables ModemManager_CFLAGS
and ModemManager_LIBS to avoid the need to call pkg-config.
...
</pre>
      </blockquote>
      <pre wrap="">
Can we simply drop the libmm-glib-dev package and put all the
development files into modemmanager-dev, like we do with the rest of
our aports?

-nc
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------F156785A014E5911E3DD6A86--


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---