keeping software forks under MacPorts repo?

[Christopher Jones]

> On 9 Nov 2019, at 5:24 pm, Ken Cunningham <ken.cunningham.webuse at gmail.com> wrote:
> 
> 
> 
>> On Nov 9, 2019, at 9:06 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
>> 
>> On Nov 9, 2019, at 11:00, Mojca Miklavec wrote:
>>> 
>>> But we would probably want to
>>> prefix the repository names (something like "fork_qt", "fork_llvm") to
>>> clearly distinguish them from our main repositories.
>> 
>> I wouldn't necessarily suggest doing that. We're not forking in order to diverge from upstream and evolve the software into a different product. We're only doing it to apply bug fixes. 
> 
> 
> if it was decided to proceed, perhaps MacPorts/qt4 might be a reasonable name for the fork …

Thats exactly my point. "MacPorts/qt4” is enough to signify its a fork. Adding “fork_” to the name is IMHO pointless and in fact adds confusion, not removes it.

Chris


> 
> the default  fork name of “qt” is not specific enough, I think.
> 
> Thanks for considering.
> 
> K

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1930 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20191109/72820923/attachment.bin>