> On Nov 13, 2016, at 6:27 AM, Rainer Müller wrote:
>
> On 2016-11-12 22:30, Ryan Schmidt wrote:
>> We do actually have a "trunk" rsync directory. Isn't the purpose of
>> that to allow users of master to selfupdate using it? I've never
>> tried it.
>
> Even if you change the rsync_dir in macpor
On 2016-11-13 10:04, Marko Käning wrote:
> Do we have a ticket for this trac-setup issue?
I was hoping we could resolve this quickly, but it does not seem to be
trivial.
I created a ticket to track this now:
https://trac.macports.org/ticket/52871
Rainer
Hi,
to summarize:
- The consensus seems to be that the feature should be in the next
release.
- We're not sure whether that next release should be 2.3.5 or 2.4, but
it should definitely come from the release branch for 2.3.x.
- There are risks associated with releasing a 2.4 that does not have
On 2016-11-12 22:30, Ryan Schmidt wrote:
> We do actually have a "trunk" rsync directory. Isn't the purpose of
> that to allow users of master to selfupdate using it? I've never
> tried it.
Even if you change the rsync_dir in macports.conf, the version on master
is always 2.3.99. This is the same
> On Nov 12, 2016, at 3:30 PM, Ryan Schmidt wrote:
>
> Precisely. Which is why we mustn't cause a downgrade to occur for users of
> master.
Conveniently, https://trac.macports.org/ticket/52855 demonstrates one problem
users will encounter if they downgrade.
Do we have a ticket for this trac-setup issue?
