On 2018-03-01 14:48, Ryan Schmidt wrote:
+license BSD-2-Clause
MacPorts doesn't know that license by that name; we call this license "BSD".
It's important to use the correct license name so that MacPorts can distribute binaries
of ports that are distributable. Changing the
On 2018-3-2 09:09 , Mojca Miklavec wrote:
> On 22 February 2018 at 21:14, Ryan Schmidt wrote:
>> On Feb 22, 2018, at 04:57, Mojca Miklavec wrote:
>>
>>> Dear Ryan,
>>>
>>> What is the current situaton with mirorring distfiles
>>
>> Unchanged. I need to create a buildworker on the buildmaster. I
On 2 March 2018 at 07:15, Joshua Root wrote:
> On 2018-3-2 08:27 , Mojca Miklavec wrote:
>> On 1 March 2018 at 20:42, Michael Dickens wrote:
>>> In the past, I've handled this situation by using the muniversal PortGroup,
>>> so that the sizeof is correct for each build independent of the other. -
On 2018-3-2 08:27 , Mojca Miklavec wrote:
> On 1 March 2018 at 20:42, Michael Dickens wrote:
>> In the past, I've handled this situation by using the muniversal PortGroup,
>> so that the sizeof is correct for each build independent of the other. - MLD
>
> I'm aware of that. I was wondering if
On Fri, 2 Mar 2018 01:44:03 +0100 Mojca Miklavec
wrote:
> On 2 March 2018 at 01:41, Perry E. Metzger wrote:
> > On Thu, 1 Mar 2018 22:25:47 +0100 Mojca Miklavec wrote:
> >> > Maybe we need more flexible (and less likely to time out) CI
> >> > than Travis can give us that
On 2 March 2018 at 01:41, Perry E. Metzger wrote:
> On Thu, 1 Mar 2018 22:25:47 +0100 Mojca Miklavec wrote:
>> > Maybe we need more flexible (and less likely to time out) CI than
>> > Travis can give us that includes things like port lint, traced
>> > builds, etc?
>>
>> That would be nice to have,
On Thu, 1 Mar 2018 22:25:47 +0100 Mojca Miklavec
wrote:
> > Maybe we need more flexible (and less likely to time out) CI than
> > Travis can give us that includes things like port lint, traced
> > builds, etc?
>
> That would be nice to have, but do you have any idea how to
On Mar 1, 2018, at 16:09, Mojca Miklavec wrote:
> On 22 February 2018 at 21:14, Ryan Schmidt wrote:
>> On Feb 22, 2018, at 04:57, Mojca Miklavec wrote:
>>
>>> Dear Ryan,
>>>
>>> What is the current situaton with mirorring distfiles
>>
>> Unchanged. I need to create a buildworker on the
On 22 February 2018 at 21:14, Ryan Schmidt wrote:
> On Feb 22, 2018, at 04:57, Mojca Miklavec wrote:
>
>> Dear Ryan,
>>
>> What is the current situaton with mirorring distfiles
>
> Unchanged. I need to create a buildworker on the buildmaster. I then need to
> deploy the buildbot configuration
Since the port is using GNU Autotools, AC_COMPILE_CHECK_SIZEOF will return one
of 2 values depending on which -arch flag is used / set / set first / some
random reason; it cannot return both values. Hence why using muniversal if
truly in doubt.
The best solution is to use pre-sized types such
On 1 March 2018 at 20:42, Michael Dickens wrote:
> In the past, I've handled this situation by using the muniversal PortGroup,
> so that the sizeof is correct for each build independent of the other. - MLD
I'm aware of that. I was wondering if there was some *proper* solution
that could allow
On 1 March 2018 at 20:23, Perry E. Metzger wrote:
> On Thu, 1 Mar 2018 08:40:51 -0800 Ken Cunningham wrote:
>> CI is not sufficient testing to commit, sadly.
>>
>> There is no xcode 9 in travis at present.
>> misses many things, like liscence etc
>> doesn't check if destrooting is right
>>
>> It's
On 1 March 2018 at 21:56, Umesh Singla wrote:
> Hi
>
> You are welcome to select multiple ideas provided you're able to communicate
> about it with mentors and propose on time. Only the best one proposal will
> be selected.
I must strongly disagree here.
OK, sure, the student *could* prepare
Hi
You are welcome to select multiple ideas provided you're able to
communicate about it with mentors and propose on time. Only the best one
proposal will be selected.
Generally it's better to pay attention to understand one project's
requirements and expectations to get started with a
On 1 March 2018 at 21:17, Abhishek Kasyap wrote:
> Can i select more than one idea in this organisation.
You can submit an arbitrary proposal. You can combine several ideas
that need less work or write a completely different proposal for
writing something that's not even listed (once you are
> On Mar 1, 2018, at 11:23 AM, Perry E. Metzger wrote:
>
> Looking over things carefully seems reasonable. A machine can't
> figure out that a Portfile should be written differently.
>
> Having to build locally in several ways seems bad. The purpose of
> automatic CI
Can i select more than one idea in this organisation.What is terms and
condition of this Gsoc project.
In the past, I've handled this situation by using the muniversal PortGroup, so
that the sizeof is correct for each build independent of the other. - MLD
On Thu, Mar 1, 2018, at 2:40 PM, Mojca Miklavec wrote:
> While checking some patches of a library I decided to try whether the
> library would
Hi,
While checking some patches of a library I decided to try whether the
library would build universally. The configure.ac part contains:
AC_COMPILE_CHECK_SIZEOF([long])
and that happily fails with
checking size of long... configure: error: cannot determine a size for long
when
On Thu, 1 Mar 2018 08:40:51 -0800 Ken Cunningham
wrote:
> CI is not sufficient testing to commit, sadly.
>
> There is no xcode 9 in travis at present.
> misses many things, like liscence etc
> doesn't check if destrooting is right
>
> It's OK for a minor version
CI is not sufficient testing to commit, sadly.
There is no xcode 9 in travis at present.
misses many things, like liscence etc
doesn't check if destrooting is right
It's OK for a minor version update of an existing port, but all new ports or
sig updates need to checked out locally, port lint
On Mar 1, 2018, at 09:01, Perry E. Metzger wrote:
> On Thu, 1 Mar 2018 08:06:05 -0600 Ryan Schmidt wrote:
>>> +github.setupstevenlovegrove Pangolin v0.5
>>
>> This causes the port's version to be "v0.5". We don't want the "v"
>> in the version, only the number. The correct way to
On Mar 1, 2018, at 09:50, Mojca Miklavec wrote:
>> The builds failed on the buildbot, which is how I noticed the problem. On
>> the buildbot, we activate the dependencies and then make sure the
>> dependencies' build dependencies are deactivated before building the port,
>> thus exposing the
On 1 March 2018 at 15:03, Ryan Schmidt wrote:
>
> On Mar 1, 2018, at 07:59, Perry E. Metzger wrote:
>> On Thu, 1 Mar 2018 07:48:35 -0600 Ryan Schmidt wrote:
+depends_lib-append port:libusb
>>>
>>> The port failed to build without pkgconfig.
>>
>> Should the CI infrastructure have noticed
On Thu, 1 Mar 2018 08:06:05 -0600 Ryan Schmidt
wrote:
> > +github.setupstevenlovegrove Pangolin v0.5
>
> This causes the port's version to be "v0.5". We don't want the "v"
> in the version, only the number. The correct way to invoke
> github.setup for this
On 1 Mar 2018, at 13:14, Ryan Schmidt wrote:
> What do you mean?
> I don't think port lint currently gives whitespace recommendations. And if it
> did, port lint still just provides suggestions that must be moderated by
> human decisions.
I just tried it and it seems
On Mar 1, 2018, at 07:08, Андрей Корнилов wrote:
> Perry E. Metzger (pmetzger) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/9fd8e12cdd62de80a694897d4ab7da3e8a6f81fb
>
> The following commit(s) were added to
On Mar 1, 2018, at 07:59, Perry E. Metzger wrote:
> On Thu, 1 Mar 2018 07:48:35 -0600 Ryan Schmidt wrote:
>>> +depends_lib-append port:libusb
>>
>> The port failed to build without pkgconfig.
>
> Should the CI infrastructure have noticed that? I've kind of been
> assuming that if CI is green
On Thu, 1 Mar 2018 07:48:35 -0600 Ryan Schmidt
wrote:
> > +depends_lib-append port:libusb
>
> The port failed to build without pkgconfig.
Should the CI infrastructure have noticed that? I've kind of been
assuming that if CI is green you can assume the thing is okay,
On Mar 1, 2018, at 07:10, Андрей Корнилов wrote:
> Perry E. Metzger (pmetzger) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/1143d9e29ce540771dbbfc578100f28ee04b3f28
>
> The following commit(s) were added to
On 28 Feb 2018, at 14:58, Ryan Schmidt wrote:
> I wouldn't completely change the whitespace of someone else's port, even
> after a maintainer timeout. But I would correct whitespace mistakes in
> someone else's port after a suitable timeout.
Shouldn't port lint be the
31 matches
Mail list logo