OK! Just submitted my first git pull — please be gentle — I think I did it
correctly, but ….
Ken
> On Oct 31, 2016, at 8:56 PM, Ryan Schmidt wrote:
>
> On Oct 31, 2016, at 22:44, Ken Cunningham
> wrote:
>>
>> I have no clue how to submit a portfile *.diff any longer (is that a sigh of
>
On Oct 31, 2016, at 22:44, Ken Cunningham
wrote:
>
> I have no clue how to submit a portfile *.diff any longer (is that a sigh of
> relief I hear?? :> ) , but hopefully this helps.
Thanks! The new way is to submit a pull request on GitHub, but I think we can
also still accept patch files atta
>
> I’d be happy to test the minimum requirements to build it, if Richard doesn’t
> beat me to it :>
>
> Get back to you in a day or two with the info.
>
Hello friends,
ran some tests with a spanking new installation of 10.6.8 and macports 2.3.4
with nothing installed
to build libsdl2 on 1
> On Oct 31, 2016, at 1:16 PM, Thibaut Paumard wrote:
>
> Le 31/10/2016 à 17:23, Lawrence Velázquez a écrit :
>>> On Oct 31, 2016, at 12:16 PM, Thibaut Paumard wrote:
>>>
Le 31/10/2016 à 17:01, René J.V. Bertin a écrit :
> On Monday October 31 2016 10:00:05 Ryan Schmidt wrote:
>
>
On Mon, Oct 31, 2016 at 1:34 PM, Bradley Giesbrecht
wrote:
> Test in pre-fetch and give ui_error.
>
> port cat pinentry-mac | grep -A6 pre-fetch
Perfect! Thanks!
Cheers
Adam
___
macports-users mailing list
macports-users@lists.macosforge.org
https://l
Test in pre-fetch and give ui_error.
port cat pinentry-mac | grep -A6 pre-fetch
Regards,
Bradley Giesbrecht (pixilla)
> On Oct 31, 2016, at 11:26 AM, Adam Mercer wrote:
>
> Hi
>
> I have some ports that are out of date due to the newer versions no
> longer building on macOS and the latest
Hi
I have some ports that are out of date due to the newer versions no
longer building on macOS and the latest version of dependencies no
longer supporting the older versions that still support macOS. I'm
working with upstream to try and resolve this but in the meantime is
there a way to mark thes
> On Oct 31, 2016, at 12:16 PM, Thibaut Paumard wrote:
>
>> Le 31/10/2016 à 17:01, René J.V. Bertin a écrit :
>>> On Monday October 31 2016 10:00:05 Ryan Schmidt wrote:
>>>
>>> This issue only affects the very small percentage of the MacPorts user
>>> population (including developers and mainta
On Monday October 31 2016 10:00:05 Ryan Schmidt wrote:
> This issue only affects the very small percentage of the MacPorts user
> population (including developers and maintainers) that clones the git
> repository. Most users will use the rsync server, on which we do generate
> portindexes for e
On 10/31/16 8:05 AM, Gustaf Neumann wrote:
> Am 30.10.16 um 21:31 schrieb David Evans:
>> Agreed, the problem here is with libsdl2. We need to understand what the
>> problem is on
>> 10.6 at least and either help upstream to fix it or fix it ourselves. If
>> all that fails
>> then maybe upstrea
Am 30.10.16 um 21:31 schrieb David Evans:
Agreed, the problem here is with libsdl2. We need to understand what the
problem is on
10.6 at least and either help upstream to fix it or fix it ourselves. If all
that fails
then maybe upstream needs to revise they're thinking on macOS compatibility.
> On Oct 31, 2016, at 4:18 AM, René J. V. Bertin wrote:
>
> Clemens Lang wrote:
>
>> If your question is not yet answered, ask on the mailing lists so it can
>> be added.
>
> I may have overlooked this, but does github have any provisions that would
> allow
> the PortIndex files to be genera
On 2016-10-31, at 2:28 AM, René J. V. Bertin wrote:
>
> Probably an open door, possibly a forbidden one: it may be relevant here to
> block concerned ports at the latest supported version for legacy platforms?
Although I think not needed for libsdl2 (which builds and works without issue
on 10
On 31/10/16 10:41, René J.V. Bertin wrote:
On Monday October 31 2016 10:49:55 Clemens Lang wrote:
Hi,
Just as with Subversion, the answer is no. Remember that the PortIndex
is specific to the macOS version you are running, so a server-generated
Ah, of course. I didn't actually know this bu
On Monday October 31 2016 10:49:55 Clemens Lang wrote:
Hi,
>Just as with Subversion, the answer is no. Remember that the PortIndex
>is specific to the macOS version you are running, so a server-generated
Ah, of course. I didn't actually know this but indeed port versions could be
specific to OS
On 31/10/16 09:49, Clemens Lang wrote:
Hi,
On Mon, Oct 31, 2016 at 10:18:42AM +0100, René J. V. Bertin wrote:
I may have overlooked this, but does github have any provisions that
would allow the PortIndex files to be generated on the server and
served with the actual repo contents? That woul
Hi,
On Mon, Oct 31, 2016 at 10:18:42AM +0100, René J. V. Bertin wrote:
> I may have overlooked this, but does github have any provisions that
> would allow the PortIndex files to be generated on the server and
> served with the actual repo contents? That would probably give a very
> significant r
David Evans wrote:
> However, sdl/sdl2 provides the only audio/video outdev that we support in
> MacPorts which means that if you have to have one or the other. Without an
> outdev, ffplay will not be configured/built and you'll have no direct way to
> play audio/video with ffmpeg.
It's been too
Clemens Lang wrote:
> If your question is not yet answered, ask on the mailing lists so it can
> be added.
I may have overlooked this, but does github have any provisions that would
allow
the PortIndex files to be generated on the server and served with the actual
repo
contents? That would pr
19 matches
Mail list logo
