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

[Rainer Müller]

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 <***@github.com>
To: ***@macports.org


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

[Rainer Müller]

Post by Rainer Müller
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

[Ryan Schmidt]

Post by Rainer Müller

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

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.

[Rainer Müller]

Post by Ryan Schmidt

Post by Rainer Müller

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

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.

Post by Ryan Schmidt
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.

Post by Ryan Schmidt
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