> On Nov 8, 2017, at 12:13 PM, Rainer Müller wrote:
>
> On 2017-11-08 17:32, Ryan Schmidt wrote:
>>
>> On Nov 8, 2017, at 08:24, Kurt Hindenburg wrote:
>>
>>> On Jun 25, 2017, at 1:52 AM, Joshua Root wrote:
>>>
On 2017-6-25 12:27 , Ryan Schmidt wrote:
> We often have this problem th
On 2017-11-08 17:29, Ryan Schmidt wrote:
>
> On Nov 8, 2017, at 09:02, Rainer Müller wrote:
>
>> On 2017-11-08 14:04, Mojca Miklavec wrote:
>>> Yes, we should prepare a PortGroup for it, I didn't start anything
>>> yet, but I could look into it. It might help to start with some list
>>> of packag
On 2017-11-08 17:32, Ryan Schmidt wrote:
>
> On Nov 8, 2017, at 08:24, Kurt Hindenburg wrote:
>
>> On Jun 25, 2017, at 1:52 AM, Joshua Root wrote:
>>
>>> On 2017-6-25 12:27 , Ryan Schmidt wrote:
We often have this problem that we forget to specify dependencies in a
python port. Python
On Nov 8, 2017, at 08:24, Kurt Hindenburg wrote:
> On Jun 25, 2017, at 1:52 AM, Joshua Root wrote:
>
>> On 2017-6-25 12:27 , Ryan Schmidt wrote:
>>> We often have this problem that we forget to specify dependencies in a
>>> python port. Python (setuptools?) helpfully automatically downloads a
On Nov 8, 2017, at 09:02, Rainer Müller wrote:
> On 2017-11-08 14:04, Mojca Miklavec wrote:
>> Yes, we should prepare a PortGroup for it, I didn't start anything
>> yet, but I could look into it. It might help to start with some list
>> of packages that support it.
>
> meson even prominently doc
> On Jun 25, 2017, at 1:52 AM, Joshua Root wrote:
>
> On 2017-6-25 12:27 , Ryan Schmidt wrote:
>> We often have this problem that we forget to specify dependencies in a
>> python port. Python (setuptools?) helpfully automatically downloads a
>> temporary copy of the dependency to use, so we m
On 2017-11-08 14:04, Mojca Miklavec wrote:
> Yes, we should prepare a PortGroup for it, I didn't start anything
> yet, but I could look into it. It might help to start with some list
> of packages that support it.
meson even prominently documents the use case for packaging:
http://mesonbuild.com/Q
On 7 November 2017 at 19:18, Ryan Schmidt wrote:
> We have a port for meson, a new build system.
>
> The libhttpseverywhere portfile uses it, and contains a lot of code for
> dealing with it.
>
> Should we have a meson portgroup to abstract away these details? Has anyone
> worked on that already?
