Thread overview | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
February 22, 2020 Hosting dub packages on public Heptapod instances? | ||||
---|---|---|---|---|
| ||||
Hi! The dub registry is currently only allowing package hosting on github, gitlab or bitbucket. This is incredibly limited and does not allow packages hosted elsewhere. This choice also limits dub to git repositories although it handles e.g. Mercurial just fine in practice. At the minimum I'd like to see support for gitlab or Heptapod instances other than just gitlab.com. My personal motivation is that I had to move my publicly visible projects from Bitbucket to my own Heptapod instance recently because Atlassian has arbitrary decided to delete a ton of projects from Bitbucket. Let's assume for a moment that a PR could be provided that adds this support. Would you want to have that feature in the dub registry in principle? |
February 22, 2020 Re: Hosting dub packages on public Heptapod instances? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Gregor Mückl | On Saturday, 22 February 2020 at 12:29:17 UTC, Gregor Mückl wrote:
> Hi!
>
> The dub registry is currently only allowing package hosting on github, gitlab or bitbucket. This is incredibly limited and does not allow packages hosted elsewhere. This choice also limits dub to git repositories although it handles e.g. Mercurial just fine in practice. At the minimum I'd like to see support for gitlab or Heptapod instances other than just gitlab.com. My personal motivation is that I had to move my publicly visible projects from Bitbucket to my own Heptapod instance recently because Atlassian has arbitrary decided to delete a ton of projects from Bitbucket.
>
> Let's assume for a moment that a PR could be provided that adds this support. Would you want to have that feature in the dub registry in principle?
Of course, I think the sole reason the support is so limited is that no one has had time to improve it.
BTW maybe instead of adding another API to the registry, a generic git solution could be added that uses the git protocol to query for SemVer tags and thus solve this problem once and for all.
|
February 22, 2020 Re: Hosting dub packages on public Heptapod instances? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Seb | On Saturday, 22 February 2020 at 12:47:31 UTC, Seb wrote:
> Of course, I think the sole reason the support is so limited is that no one has had time to improve it.
>
> BTW maybe instead of adding another API to the registry, a generic git solution could be added that uses the git protocol to query for SemVer tags and thus solve this problem once and for all.
Fine per se to use the VCS protocol instead of the hosting site, but note this still means you need to support multiple options. Not everyone uses git ;-)
|
February 22, 2020 Re: Hosting dub packages on public Heptapod instances? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joseph Rushton Wakeling | On Saturday, 22 February 2020 at 16:26:06 UTC, Joseph Rushton Wakeling wrote:
> On Saturday, 22 February 2020 at 12:47:31 UTC, Seb wrote:
>> Of course, I think the sole reason the support is so limited is that no one has had time to improve it.
>>
>> BTW maybe instead of adding another API to the registry, a generic git solution could be added that uses the git protocol to query for SemVer tags and thus solve this problem once and for all.
>
> Fine per se to use the VCS protocol instead of the hosting site, but note this still means you need to support multiple options. Not everyone uses git ;-)
Some of use Fossil, enjoying the option to easily write extensions in D.
|
February 23, 2020 Re: Hosting dub packages on public Heptapod instances? | ||||
---|---|---|---|---|
| ||||
Posted in reply to bachmeier | On Saturday, 22 February 2020 at 17:29:16 UTC, bachmeier wrote:
> Some of use Fossil, enjoying the option to easily write extensions in D.
I knew there was a reason why I liked you :-)
|
February 23, 2020 Re: Hosting dub packages on public Heptapod instances? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Gregor Mückl | On Saturday, 22 February 2020 at 12:29:17 UTC, Gregor Mückl wrote:
> Hi!
>
> The dub registry is currently only allowing package hosting on github, gitlab or bitbucket. This is incredibly limited and does not allow packages hosted elsewhere. This choice also limits dub to git repositories although it handles e.g. Mercurial just fine in practice. At the minimum I'd like to see support for gitlab or Heptapod instances other than just gitlab.com. My personal motivation is that I had to move my publicly visible projects from Bitbucket to my own Heptapod instance recently because Atlassian has arbitrary decided to delete a ton of projects from Bitbucket.
>
> Let's assume for a moment that a PR could be provided that adds this support. Would you want to have that feature in the dub registry in principle?
Side information, as dub client is also able to speak Maven, you can host your Dub packages on any Maven registry like Nexus or Artifactory.
Kind regards
Andre
|
February 24, 2020 Re: Hosting dub packages on public Heptapod instances? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joseph Rushton Wakeling | On Saturday, 22 February 2020 at 16:26:06 UTC, Joseph Rushton Wakeling wrote:
> On Saturday, 22 February 2020 at 12:47:31 UTC, Seb wrote:
>> Of course, I think the sole reason the support is so limited is that no one has had time to improve it.
>>
>> BTW maybe instead of adding another API to the registry, a generic git solution could be added that uses the git protocol to query for SemVer tags and thus solve this problem once and for all.
>
> Fine per se to use the VCS protocol instead of the hosting site, but note this still means you need to support multiple options. Not everyone uses git ;-)
Yes, the main problem then is getting appropriate client libraries for all reasonable options... this alone seems like a huge undertaking to me. The scope is definitely beyond whatever time I can make for writing a patch against the dub registry.
I'd personally be mostly content if I can find the time to patch it all up in a way that Gitlab instances other than gitlab.com can be used. As I see it, this already requires a couple of UI changes that would also be needed for VCS protocol approach.
|
Copyright © 1999-2021 by the D Language Foundation