I also agree with what you wrote. The three ports
- gnupg-legacy (possibly call this gnupg14 - since this is unlikely to
change)
- gnupg-stable
- gnupg-current
should all conflict with each other.
I'm in favour of keeping version numbers out of port names because if
upstream iterate quickly you'
> On Sep 8, 2017, at 5:04 PM, Umesh Singla wrote:
>
> On Sat, Sep 9, 2017 at 3:40 AM, Rainer Müller wrote:
> On 2017-09-08 23:33, Umesh Singla wrote:
> > When I run the `migrate` action with only one port (expat) installed, I
> > get the following:
> >
> > $ sudo ./bin/port migrate
> >
> > Takin
> On Sep 9, 2017, at 9:19 AM, Rainer Müller wrote:
>
> On 2017-09-07 22:25, Wahlstedt Jyrki wrote:
>> Dear all,
>> as many of you have already seen, I’ve dropped nearly all of my
>> maintainerships. I’ve been involved in this community over ten years,
>> and now I feel I want to do some things p
On 2017-09-07 22:25, Wahlstedt Jyrki wrote:
> Dear all,
> as many of you have already seen, I’ve dropped nearly all of my
> maintainerships. I’ve been involved in this community over ten years,
> and now I feel I want to do some things preventing me from the
> commitment to do this anymore on a con
On Sep 8, 2017, at 17:50, Rainer Müller wrote:
> On 2017-09-08 18:48, Daniel J. Luke wrote:
>> One solution might be to separate the build/distfile mirroring from the
>> portfile mirroring. You could probably even do that by running separate
>> rsync's for those on your home connection and doing
On Friday September 08 2017 21:06:35 Jeremy Huddleston Sequoia wrote:
> The reason for this is that many OSS projects based on autoconf, cmake, etc
> have an assumption baked into the build system that the SDK matches the
> minimum level of support.
Well, I think that *is* the easier/safer as