Sourceforge projects
Steven Schveighoffer
schveiguy at gmail.com
Thu Oct 15 13:05:09 UTC 2020
On 10/14/20 6:21 PM, norm wrote:
> On Wednesday, 14 October 2020 at 16:41:26 UTC, rikki cattermole wrote:
>> On 15/10/2020 2:18 AM, Vitaly Livshic wrote:
>>> Restriction on a specific sites and version control is unexpected for
>>> open-source project. Is there are any possibility to use sourceforge
>>> or non-git repositories?
>>
>> It can be completely expected the current behavior.
>>
>> Version control systems like git don't provide a standard way via a
>> web server to obtain a compressed archive at a specific
>> commit/tag/branch.
>>
>> Nor does it provide access to meta-data. Like tags or branches.
>>
>> You can get this information and archive by checking out the
>> repository, which is more complex to perform and requires the VCS to
>> be installed on the node that does it.
>>
>> Here are the source code for the VCS suppliers that dub-registry
>> supports[0].
>>
>> Note: I would recommend heavily to not create new projects on SF, they
>> have been known in recent years to do some nasty stuff with any
>> binaries that you may upload.
>>
>> [0]
>> https://github.com/dlang/dub-registry/tree/master/source/dubregistry/repositories
>>
>
>
> This sounds like an arbitrary limitation in dub tbh and nothing to do
> with git. The standard git commands work with SF hosted repos just like
> they do with github, gitlab and bitbucket.
Dub does not use git commands to introspect what versions exist, etc. It
uses web APIs that are provided by the hosting systems. It's just the
case that dub doesn't have support for those other systems. If you
submit a PR to add sourceforge support, I'm sure it would be accepted.
Here are the objects which deal with the different repository types:
https://github.com/dlang/dub-registry/tree/master/source/dubregistry/repositories
> Git archive will get you a compressed archive if all you want are the
> files, but why does dub want to do this?
>
> Git can clone the metadata without checking out HEAD if that is all dub
> requires, which sounds more like what the dub registry requires.
I'm sure also, improvements to dub that allow fetching the info through
a git interface would be accepted as well.
-Steve
More information about the Digitalmars-d
mailing list