[Gambas-devel] gambas-cygport git project

PICCORO McKAY Lenz mckaygerhard at ...176...
Tue Aug 15 21:20:24 CEST 2017


umm you have right!.. so then for each port gambas group can have
projects per ports..

O.o!

this "gambas" gitlab gropu, growup so faster!
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com


2017-08-15 15:18 GMT-04:00 Bastian Germann <bastiangermann at ...754...>:
> I have created merge requests to get the patches upstream (except
> gambas3-libpq.patch). The cygport defines the sourceforge release
> mirrors as the place to download the Gambas source files from, so it
> does not need them nearby in the file system, i.e. it is not a good idea
> to keep it as a branch in the gambas repository. It is possible but not
> idiomatic to have branches with no common history (orphans) in git.
>
> Also I want to be able to set git tags, which are global for a repo. It
> would be bad to have the Cygwin package version numbers appear in one
> list with the Gambas version numbers.
>
> I can define git as download source in the cygport instead of
> sourceforge as well, which I do for development purposes.
>
> Am 15.08.2017 um 20:57 schrieb PICCORO McKAY Lenz:
>> umm in that cases, another project under the "gambas" group can exist
>> but i thing its not necesary.. i explain me:
>>
>> its better a branch, due i guess your Cygwin need the gambas files..
>> so with a brand you can play with devel version or stable lasted and
>> your patches can be apply directly or not depends on merged changes...
>>
>> lest wait what said benoit and others..
>> Lenz McKAY Gerardo (PICCORO)
>> http://qgqlochekone.blogspot.com
>>
>>
>> 2017-08-15 12:06 GMT-04:00 Bastian Germann <bastiangermann at ...754...>:
>>> The gambas3.cygport file in the repo is used with cygport [0] to
>>> generate all the gambas3* packages that are available in the Cygwin
>>> package repository [1].
>>>
>>> I compile the packages in Cygwin, so no cross compilation is involved.
>>>
>>> Paint.NET (I cannot get any sources to build) needs the .NET environment
>>> to run, which is also some hundreds of MB, so your example is flawed.
>>> And it is Windows-only software, whereas Gambas expects a unix-like
>>> environment to run...
>>>
>>> [0] https://github.com/cygwinports/cygport
>>> [1] https://cygwin.com/cgi-bin2/package-grep.cgi?grep=gambas3
>>>
>>> Am 15.08.2017 um 16:11 schrieb PICCORO McKAY Lenz:
>>>> i do not use deeply those but how does work for gambas? can you explain more !?
>>>>
>>>> as i understand cywing download a "lot" of bytes to have pieces
>>>> working for a single package development.. just imaginate: i want to
>>>> build paint.net inside linux for guiindows.. that produces a only 6 Mb
>>>> file.. good.. the cywing environment are very huge for that..
>>>> Lenz McKAY Gerardo (PICCORO)
>>>> http://qgqlochekone.blogspot.com
>>>>
>>>>
>>>> 2017-08-15 5:45 GMT-04:00 Bastian Germann <bastiangermann at ...754...>:
>>>>> Hi,
>>>>>
>>>>> the Gambas Cygwin package that I maintain is generated from a cygport
>>>>> file that is available on GitLab. As there is a gambas organization now,
>>>>> maybe you want to have https://gitlab.com/bgermann/gambas-cygport
>>>>> available there. If so, you can add me to the organization and I will
>>>>> move it.
>>>>>
>>>>> Regards,
>>>>> Bastian
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gambas-devel mailing list
> Gambas-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-devel




More information about the Devel mailing list