[Gambas-user] Switching to GitLab

[PICCORO McKAY Lenz]

2017-08-16 15:30 GMT-04:00 Adrien Prokopowicz <adrien.prokopowicz at ...626...>:
>> It's because the download tool of GitLab downloads everything (especially
>> the 'MakeWebSite' project that has a lot big files in it), whereas the "make
>> dist-bzip2" command only package what is relevant to compile and install
>> Gambas.
mayor software are prepared separated.. and due the nature of
subversion (and limist) all was shiped in a isolated repository..

modern software are made, as each product have their own repository..

>>
>> If no 'git' solution exist, maybe I will have to make these source
>> packages manually again, and store them on Sourceforge as usual...
>>
>
> While there are no "git" solutions for this, maybe we should put the website
> in
> its own repository, apart from the rest of the source tree ?
> Same goes for the wiki, the bugtracker, etc.
its the most obvius and the right way.. the website there nothig to do
with the code of the softwafre..

>
> (I can move it into a new repository without losing the history, if you
> want)
>
> As a side-note, we can also use GitLab's Pipelines feature to run the make
> dist-bzip2 command and store the results every time we tag a new release
> (we can also use it to distribute compiled binaries if we want).
>
> --
> Adrien Prokopowicz
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gambas-user mailing list
> Gambas-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-user