Fwd: [GitHub] Subscribed to macports/macports-legacy-support notifications

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Fwd: [GitHub] Subscribed to macports/macports-legacy-support notifications

Rainer Müller-4
What is the plan? Should we also connect this new repository with Trac?

Rainer


-------- Forwarded Message --------
Subject: [GitHub] Subscribed to macports/macports-legacy-support
notifications
Date: Wed, 07 Nov 2018 12:47:03 -0800
From: GitHub <[hidden email]>
To: [hidden email]


Hey there, we’re just writing to let you know that you’ve been
automatically subscribed to a repository on GitHub.

    macports/macports-legacy-support
    MacPorts support for missing functions in legacy macOS versions
    https://github.com/macports/macports-legacy-support

Reply | Threaded
Open this post in threaded view
|

Re: Fwd: [GitHub] Subscribed to macports/macports-legacy-support notifications

Rainer Müller-4
On 07.11.18 22:10, Rainer Müller wrote:
> What is the plan? Should we also connect this new repository with Trac?

Ah, just found the ticket:
https://trac.macports.org/ticket/57537

Rainer
Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Subscribed to macports/macports-legacy-support notifications

Ryan Schmidt-24


On Nov 7, 2018, at 15:22, Rainer Müller wrote:

> On 07.11.18 22:10, Rainer Müller wrote:
>> What is the plan? Should we also connect this new repository with Trac?
>
> Ah, just found the ticket:
> https://trac.macports.org/ticket/57537

Yes, that would be a good idea. Do we also want a new component in Trac for this? I think maybe yes. Or do we group it in with contrib?

It's probably a good idea for each project to get its own repo like this. I feel that we should probably break individual projects out of macports-contrib into their own repos as well.

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Subscribed to macports/macports-legacy-support notifications

Rainer Müller-4
On 07.11.18 22:31, Ryan Schmidt wrote:
>
>
> On Nov 7, 2018, at 15:22, Rainer Müller wrote:
>
>> On 07.11.18 22:10, Rainer Müller wrote:
>>> What is the plan? Should we also connect this new repository with Trac?
>>
>> Ah, just found the ticket:
>> https://trac.macports.org/ticket/57537

The new repository is now also connected to Trac via the usual WebHook.
It is not connected to buildbot or pr-bot, as I have no idea if these
services would be ready for it or if it would even be useful.

> Yes, that would be a good idea. Do we also want a new component in Trac for this? I think maybe yes. Or do we group it in with contrib?

As ports are expected to download this, a separate repository makes sense.

> It's probably a good idea for each project to get its own repo like this. I feel that we should probably break individual projects out of macports-contrib into their own repos as well.
+1

Rainer