From adrien.prokopowicz at ...176... Fri Aug 11 23:24:54 2017 From: adrien.prokopowicz at ...176... (Adrien Prokopowicz) Date: Fri, 11 Aug 2017 23:24:54 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: References: Message-ID: Le Sat, 22 Jul 2017 20:35:17 +0200, Adrien Prokopowicz a ?crit: > Hello everyone, > > In an effort to both switch the Gambas project versioning to Git, and to > move away > from Sourceforge, I imported the whole repository to GitLab. You can > see it here : > > https://gitlab.com/prokopyl/gambas > > From what I see, all history, commits, tags and branches have been > successfully > imported, and authors have been correctly mapped from their Sourceforge > usernames to > Git full names and emails (the SVN/Git mapping file is attached). > > I know there has been some GitHub vs. GitLab debate on the mailing list > somewhere, > but it didn't seem to have produced anything, so I just picked one. > Since nothing I have done is GitLab-specific (it's just a plain Git > repository for now), > we can easily use GitHub too. > I personally picked GitLab simply because we can easily retrieve data > (issues, wiki and such) > from a generated archive if we ever want to switch, and their > integrated CI solution > seems less restricted than Travis (but I didn't go that far with it). > > For now, all I did was cloning the entire SVN repo on the server that > hosts the > playground (for its symmetric 100Mbit/s connection :) ), then using > git-svn to > create a git repo from the clone, and then push it all to GitLab. > > I'm currently trying to set up Continuous Integration to generate Ubuntu > packages, and > maybe for more distributions later (RHEL/CentOS, Debian, ArchLinux, ?). > > I know we won't switch to Git right now, I'm at least waiting for 3.10 > to be released > so everything can calm down. :) > However I would like your feedback : what do you think is needed to make > Gambas > successfully switch to Git ? (Whichever host we end up choosing). > > Regards, So I just took some time to clean up the repository, and I implemented the workflow we discussed in previous messages, with one little exception : the master branch is the development branch, and I created a "stable" branch, which currently contains the newly-released 3.10.0 version. This way, the master branch works exactly like the old "trunk", which makes the migration easier (both form a svn-git and a developer standpoint). I also removed all the old version branches[0] and turned them into actual tags instead[1]. I also transferred the repo from my personal account to a new group : https://gitlab.com/gambas-basic/gambas I invited Beno?t as an owner, and Laurent and Fabien as developers. If other regular contributors / component maintainers want to join, just ask me here. :-) I would like the group to be simply called "gambas", but for that Beno?t needs to change his username on GitLab first (right now it conflicts :-) ). Now that the repo is organized and usable, the only thing left to do to fully switch to Git(Lab) is to write the contributing guides and update the wiki, so that everybody can configure their clients and start working again. As a side note, it is amusing that even though the repo wasn't fully migrated, there is already enough work done in it to make examples for the git workflow : - Last week, I made some small changes to how the WITH keyword works (see bug #1131 on the tracker[2]), but since these changes affect the compiler and the generated Gambas bytecode, I wanted to have Beno?t review it, so I made a new temporary branch (from master), and created a Merge Request[3] ! - I also created another experimental branch[4] to try and build Gambas with CMake instead. This is an old project of mine that was never completed, but I decided to push it on the repo for experience sharing, because : - Laurent Carlier wants to try and use Meson for building Gambas, but since he had no access to the repository at all, he forked it to a personal repository[5]. This way, when he will be done he can create a Merge Request to merge it back into the main repository, which is a great way for other people to contribute to Gambas. :-) You can also see all the branch shenanigans on the fancy graph here : https://gitlab.com/gambas-basic/gambas/network/master [0] https://gitlab.com/gambas-basic/gambas/branches [1] https://gitlab.com/gambas-basic/gambas/tags [2] http://gambaswiki.org/bugtracker/edit?object=BUG.1131&from=L21haW4- [3] https://gitlab.com/gambas-basic/gambas/merge_requests/1 [4] https://gitlab.com/gambas-basic/gambas/tree/cmake [5] https://gitlab.com/lordheavy/gambas/commits/meson-test -- Adrien Prokopowicz From gambas at ...1... Fri Aug 11 23:54:46 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Fri, 11 Aug 2017 23:54:46 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: References: Message-ID: Le 11/08/2017 ? 23:24, Adrien Prokopowicz a ?crit : > > So I just took some time to clean up the repository, and I implemented the > workflow we discussed in previous messages, with one little exception : the > master branch is the development branch, and I created a "stable" > branch, which > currently contains the newly-released 3.10.0 version. > This way, the master branch works exactly like the old "trunk", which > makes the > migration easier (both form a svn-git and a developer standpoint). > > I also removed all the old version branches[0] and turned them into > actual tags > instead[1]. > > I also transferred the repo from my personal account to a new group : > https://gitlab.com/gambas-basic/gambas > > I invited Beno?t as an owner, and Laurent and Fabien as developers. > If other regular contributors / component maintainers want to join, > just ask me here. :-) > > I would like the group to be simply called "gambas", but for that Beno?t > needs > to change his username on GitLab first (right now it conflicts :-) ). > > Now that the repo is organized and usable, the only thing left to do to > fully > switch to Git(Lab) is to write the contributing guides and update the wiki, > so that everybody can configure their clients and start working again. > > As a side note, it is amusing that even though the repo wasn't fully > migrated, > there is already enough work done in it to make examples for the git > workflow : > > - Last week, I made some small changes to how the WITH keyword works > (see bug > #1131 on the tracker[2]), but since these changes affect the compiler > and the > generated Gambas bytecode, I wanted to have Beno?t review it, so I made > a new temporary branch (from master), and created a Merge Request[3] ! > - I also created another experimental branch[4] to try and build Gambas > with > CMake instead. This is an old project of mine that was never > completed, but > I decided to push it on the repo for experience sharing, because : > - Laurent Carlier wants to try and use Meson for building Gambas, > but since he had no access to the repository at all, he forked it to a > personal repository[5]. > This way, when he will be done he can create a Merge Request to merge it > back into the main repository, which is a great way for other people to > contribute to Gambas. :-) > > You can also see all the branch shenanigans on the fancy graph here : > https://gitlab.com/gambas-basic/gambas/network/master > > [0] https://gitlab.com/gambas-basic/gambas/branches > [1] https://gitlab.com/gambas-basic/gambas/tags > [2] http://gambaswiki.org/bugtracker/edit?object=BUG.1131&from=L21haW4- > [3] https://gitlab.com/gambas-basic/gambas/merge_requests/1 > [4] https://gitlab.com/gambas-basic/gambas/tree/cmake > [5] https://gitlab.com/lordheavy/gambas/commits/meson-test Is it possible to transfer the repository to gambas/gambas ? What should I do for that? -- Beno?t Minisini From tmorehen at ...755... Fri Aug 11 23:54:46 2017 From: tmorehen at ...755... (Tony Morehen) Date: Fri, 11 Aug 2017 17:54:46 -0400 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: References: Message-ID: <0174ad10-69a1-9510-f5df-2e6c362f6dc2@...755...> Adrien, Great work! I'd like to become a contributor/developer. I'm retired so I have time to spare. My programming experience goes back almost 40 years, to a PDP-9. My C is very rusty, but my basic and Gambas is current. On 2017-08-11 05:24 PM, Adrien Prokopowicz wrote: > Le Sat, 22 Jul 2017 20:35:17 +0200, Adrien Prokopowicz > a ?crit: > >> Hello everyone, >> >> In an effort to both switch the Gambas project versioning to Git, and >> to move away >> from Sourceforge, I imported the whole repository to GitLab. You can >> see it here : >> >> https://gitlab.com/prokopyl/gambas >> >> From what I see, all history, commits, tags and branches have been >> successfully >> imported, and authors have been correctly mapped from their >> Sourceforge usernames to >> Git full names and emails (the SVN/Git mapping file is attached). >> >> I know there has been some GitHub vs. GitLab debate on the mailing >> list somewhere, >> but it didn't seem to have produced anything, so I just picked one. >> Since nothing I have done is GitLab-specific (it's just a plain Git >> repository for now), >> we can easily use GitHub too. >> I personally picked GitLab simply because we can easily retrieve data >> (issues, wiki and such) >> from a generated archive if we ever want to switch, and their >> integrated CI solution >> seems less restricted than Travis (but I didn't go that far with it). >> >> For now, all I did was cloning the entire SVN repo on the server that >> hosts the >> playground (for its symmetric 100Mbit/s connection :) ), then using >> git-svn to >> create a git repo from the clone, and then push it all to GitLab. >> >> I'm currently trying to set up Continuous Integration to generate >> Ubuntu packages, and >> maybe for more distributions later (RHEL/CentOS, Debian, ArchLinux, ?). >> >> I know we won't switch to Git right now, I'm at least waiting for >> 3.10 to be released >> so everything can calm down. :) >> However I would like your feedback : what do you think is needed to >> make Gambas >> successfully switch to Git ? (Whichever host we end up choosing). >> >> Regards, > > So I just took some time to clean up the repository, and I implemented > the > workflow we discussed in previous messages, with one little exception > : the > master branch is the development branch, and I created a "stable" > branch, which > currently contains the newly-released 3.10.0 version. > This way, the master branch works exactly like the old "trunk", which > makes the > migration easier (both form a svn-git and a developer standpoint). > > I also removed all the old version branches[0] and turned them into > actual tags > instead[1]. > > I also transferred the repo from my personal account to a new group : > https://gitlab.com/gambas-basic/gambas > > I invited Beno?t as an owner, and Laurent and Fabien as developers. > If other regular contributors / component maintainers want to join, > just ask me here. :-) > > I would like the group to be simply called "gambas", but for that > Beno?t needs > to change his username on GitLab first (right now it conflicts :-) ). > > Now that the repo is organized and usable, the only thing left to do > to fully > switch to Git(Lab) is to write the contributing guides and update the > wiki, > so that everybody can configure their clients and start working again. > > As a side note, it is amusing that even though the repo wasn't fully > migrated, > there is already enough work done in it to make examples for the git > workflow : > > - Last week, I made some small changes to how the WITH keyword works > (see bug > #1131 on the tracker[2]), but since these changes affect the > compiler and the > generated Gambas bytecode, I wanted to have Beno?t review it, so I made > a new temporary branch (from master), and created a Merge Request[3] ! > - I also created another experimental branch[4] to try and build > Gambas with > CMake instead. This is an old project of mine that was never > completed, but > I decided to push it on the repo for experience sharing, because : > - Laurent Carlier wants to try and use Meson for building Gambas, > but since he had no access to the repository at all, he forked it to a > personal repository[5]. > This way, when he will be done he can create a Merge Request to > merge it > back into the main repository, which is a great way for other people to > contribute to Gambas. :-) > > You can also see all the branch shenanigans on the fancy graph here : > https://gitlab.com/gambas-basic/gambas/network/master > > [0] https://gitlab.com/gambas-basic/gambas/branches > [1] https://gitlab.com/gambas-basic/gambas/tags > [2] http://gambaswiki.org/bugtracker/edit?object=BUG.1131&from=L21haW4- > [3] https://gitlab.com/gambas-basic/gambas/merge_requests/1 > [4] https://gitlab.com/gambas-basic/gambas/tree/cmake > [5] https://gitlab.com/lordheavy/gambas/commits/meson-test From adrien.prokopowicz at ...176... Sat Aug 12 00:31:43 2017 From: adrien.prokopowicz at ...176... (Adrien Prokopowicz) Date: Sat, 12 Aug 2017 00:31:43 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: References: Message-ID: Le Fri, 11 Aug 2017 23:54:46 +0200, Beno?t Minisini a ?crit: > > Is it possible to transfer the repository to gambas/gambas ? What should > I do for that? > The proper way to do this would be to keep the repository on the group (I invited you as an owner, so you should have full access to the group too), and then change your username (you'll find it under your icon > Settings > Account), so the group can be renamed "gambas", and so the repository will be named gambas/gambas. This way, we can put all gambas-related projects and repositories under a single group (website, wiki, bugtracker, playground, etc.), as well as the regularly contributing developers. However, if you wish to have the repository on your personal account instead, I can initiate a repository transfer. You will then receive a notification to complete it. -- Adrien Prokopowicz From mckaygerhard at ...176... Sat Aug 12 03:21:32 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Fri, 11 Aug 2017 21:21:32 -0400 Subject: [Gambas-devel] Gambas to Git(Lab) Message-ID: > > Is it possible to transfer the repository to gambas/gambas ? What should > I do for that? > > -- > Beno?t Minisini Benoit, the proper way its like Adrian said: Puting the personal user as "gambas" makes it look like a dictatorship, everyone uses their identification appropriately, and "gambas" is a working group of a complete environment .. under this is the repository "gambas" and other future projects, is the right way.. also for the integration, the gitlab has a issue redirection in settings->integration->services * custom issue tracker : to made the gambas bugtraker the main when user click on "issues" * external wiki : to made a redirection to gambaswiki when somebody click on "wiki" * email on push : as do in old svn, sends mails on each push/pull/commits From gambas at ...1... Sat Aug 12 09:07:33 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 09:07:33 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: References: Message-ID: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> Le 12/08/2017 ? 00:31, Adrien Prokopowicz a ?crit : > Le Fri, 11 Aug 2017 23:54:46 +0200, Beno?t Minisini > a ?crit: >> >> Is it possible to transfer the repository to gambas/gambas ? What >> should I do for that? >> > > The proper way to do this would be to keep the repository on the > group (I invited you as an owner, so you should have full access to > the group too), and then change your username (you'll find it under > your icon > Settings > Account), OK, done. > so the group can be renamed "gambas", and so the repository will be > named gambas/gambas. OK. done. > > This way, we can put all gambas-related projects and repositories > under a single group (website, wiki, bugtracker, playground, etc.), > as well as the regularly contributing developers. > > However, if you wish to have the repository on your personal account > instead, I can initiate a repository transfer. You will then receive > a notification to complete it. > -- Beno?t Minisini From gambas at ...1... Sat Aug 12 09:08:49 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 09:08:49 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> References: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> Message-ID: <043b5e30-a62f-414c-98f9-66dce974e580@...1...> Le 12/08/2017 ? 09:07, Beno?t Minisini via Gambas-devel a ?crit : >> >> The proper way to do this would be to keep the repository on the >> group (I invited you as an owner, so you should have full access to >> the group too), and then change your username (you'll find it under >> your icon > Settings > Account), > > OK, done. > >> so the group can be renamed "gambas", and so the repository will be >> named gambas/gambas. > > OK. done. > Now, how to update the git repository to the latest svn? -- Beno?t Minisini From gambas at ...1... Sat Aug 12 09:12:28 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 09:12:28 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: <043b5e30-a62f-414c-98f9-66dce974e580@...1...> References: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> <043b5e30-a62f-414c-98f9-66dce974e580@...1...> Message-ID: <7c2defaf-1b3f-7ab3-32b8-5ba96c3748b6@...1...> Le 12/08/2017 ? 09:08, Beno?t Minisini a ?crit : > Le 12/08/2017 ? 09:07, Beno?t Minisini via Gambas-devel a ?crit : >>> >>> The proper way to do this would be to keep the repository on the >>> group (I invited you as an owner, so you should have full access to >>> the group too), and then change your username (you'll find it under >>> your icon > Settings > Account), >> >> OK, done. >> >>> so the group can be renamed "gambas", and so the repository will be >>> named gambas/gambas. >> >> OK. done. >> > > Now, how to update the git repository to the latest svn? > Aow. It is already up to date? -- Beno?t Minisini From gambas at ...1... Sat Aug 12 09:17:58 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 09:17:58 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: <7c2defaf-1b3f-7ab3-32b8-5ba96c3748b6@...1...> References: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> <043b5e30-a62f-414c-98f9-66dce974e580@...1...> <7c2defaf-1b3f-7ab3-32b8-5ba96c3748b6@...1...> Message-ID: <2b80b59e-d0eb-9d6d-adb0-2b2507c32b94@...1...> Le 12/08/2017 ? 09:12, Beno?t Minisini via Gambas-devel a ?crit : > Le 12/08/2017 ? 09:08, Beno?t Minisini a ?crit : >> Le 12/08/2017 ? 09:07, Beno?t Minisini via Gambas-devel a ?crit : >>>> >>>> The proper way to do this would be to keep the repository on the >>>> group (I invited you as an owner, so you should have full access to >>>> the group too), and then change your username (you'll find it under >>>> your icon > Settings > Account), >>> >>> OK, done. >>> >>>> so the group can be renamed "gambas", and so the repository will be >>>> named gambas/gambas. >>> >>> OK. done. >>> >> >> Now, how to update the git repository to the latest svn? >> > > Aow. It is already up to date? > Now there is something I don't understand: - How can I make the 3.10.0 tag? From which branch? - Where are the branches of all stable versions? (3.10, 3.9, 3.8...) -- Beno?t Minisini From gambas at ...1... Sat Aug 12 09:20:11 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 09:20:11 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: <2b80b59e-d0eb-9d6d-adb0-2b2507c32b94@...1...> References: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> <043b5e30-a62f-414c-98f9-66dce974e580@...1...> <7c2defaf-1b3f-7ab3-32b8-5ba96c3748b6@...1...> <2b80b59e-d0eb-9d6d-adb0-2b2507c32b94@...1...> Message-ID: <7fe2e6e3-5839-3c44-0f18-083d93a7416d@...1...> Le 12/08/2017 ? 09:17, Beno?t Minisini a ?crit : > Le 12/08/2017 ? 09:12, Beno?t Minisini via Gambas-devel a ?crit : >> Le 12/08/2017 ? 09:08, Beno?t Minisini a ?crit : >>> Le 12/08/2017 ? 09:07, Beno?t Minisini via Gambas-devel a ?crit : >>>>> >>>>> The proper way to do this would be to keep the repository on the >>>>> group (I invited you as an owner, so you should have full access to >>>>> the group too), and then change your username (you'll find it under >>>>> your icon > Settings > Account), >>>> >>>> OK, done. >>>> >>>>> so the group can be renamed "gambas", and so the repository will be >>>>> named gambas/gambas. >>>> >>>> OK. done. >>>> >>> >>> Now, how to update the git repository to the latest svn? >>> >> >> Aow. It is already up to date? >> > > Now there is something I don't understand: > > - How can I make the 3.10.0 tag? From which branch? > > - Where are the branches of all stable versions? (3.10, 3.9, 3.8...) > Very strange: 3.10.0 tag is present in the "tags" section of the repository, but not when you pop down the list "switch branch/tag"... -- Beno?t Minisini From adrien.prokopowicz at ...176... Sat Aug 12 09:49:18 2017 From: adrien.prokopowicz at ...176... (Adrien Prokopowicz) Date: Sat, 12 Aug 2017 09:49:18 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: <7fe2e6e3-5839-3c44-0f18-083d93a7416d@...1...> References: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> <043b5e30-a62f-414c-98f9-66dce974e580@...1...> <7c2defaf-1b3f-7ab3-32b8-5ba96c3748b6@...1...> <2b80b59e-d0eb-9d6d-adb0-2b2507c32b94@...1...> <7fe2e6e3-5839-3c44-0f18-083d93a7416d@...1...> Message-ID: Le Sat, 12 Aug 2017 09:20:11 +0200, Beno?t Minisini a ?crit: > Le 12/08/2017 ? 09:17, Beno?t Minisini a ?crit : >> Le 12/08/2017 ? 09:12, Beno?t Minisini via Gambas-devel a ?crit : >>> Le 12/08/2017 ? 09:08, Beno?t Minisini a ?crit : >>>> Le 12/08/2017 ? 09:07, Beno?t Minisini via Gambas-devel a ?crit : >>>>>> >>>>>> The proper way to do this would be to keep the repository on the >>>>>> group (I invited you as an owner, so you should have full access to >>>>>> the group too), and then change your username (you'll find it under >>>>>> your icon > Settings > Account), >>>>> >>>>> OK, done. >>>>> >>>>>> so the group can be renamed "gambas", and so the repository will be >>>>>> named gambas/gambas. >>>>> >>>>> OK. done. >>>>> Nice, thank you ! >>>> >>>> Now, how to update the git repository to the latest svn? >>>> >>> >>> Aow. It is already up to date? Yes. I have a script running hourly on the playground's server to keep it updated. :-) >>> >> Now there is something I don't understand: >> - How can I make the 3.10.0 tag? From which branch? >> - Where are the branches of all stable versions? (3.10, 3.9, 3.8...) >> > Very strange: 3.10.0 tag is present in the "tags" section of the > repository, but not when you pop down the list "switch branch/tag"... It's there, but the list isn't sorted in natural order, so it's right after the 3.1.0 version. I didn't push the branches for the stable versions, since the tags have the same purpose : you can switch to any tag, and create a branch from there if you want to make changes to an older version. (Actually, you can switch to any commit you want and create a branch from there : commits are kind of like ref-counted, and a tag is just a named reference to a commit). However, if I missed something and there is something needed in these branches, I can push them back. For tagging new releases, as we've discussed in previous messages, it's all done from the "stable" branch : right now it contains the 3.10.0 version, you can either commit directly to it or cherry-pick commits from the master branch (i.e. just take specific commits instead of the whole branch, if you want only the bugfixes to tag a patch release, say 3.10.1). You can also merge the master branch into stable, which will apply all the commits the stable branch didn't have, in order to tag a new release, say 3.11. Once you're done and the stable branch contains what you want to release, you just have to create an annotated tag[0]. (Annotated tags have checksums and can be signed, unlike simple tags which are just pointers). And then it's done. :-) [0] https://git-scm.com/book/en/v2/Git-Basics-Tagging -- Adrien Prokopowicz From gambas at ...1... Sat Aug 12 10:04:39 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 10:04:39 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: References: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> <043b5e30-a62f-414c-98f9-66dce974e580@...1...> <7c2defaf-1b3f-7ab3-32b8-5ba96c3748b6@...1...> <2b80b59e-d0eb-9d6d-adb0-2b2507c32b94@...1...> <7fe2e6e3-5839-3c44-0f18-083d93a7416d@...1...> Message-ID: <22704d0c-fb06-57a1-a847-9ac7e1231fc5@...1...> Le 12/08/2017 ? 09:49, Adrien Prokopowicz a ?crit : >> Very strange: 3.10.0 tag is present in the "tags" section of the >> repository, but not when you pop down the list "switch >> branch/tag"... > > It's there, but the list isn't sorted in natural order, so it's right > after the 3.1.0 version. Ha! > > I didn't push the branches for the stable versions, since the tags > have the same purpose : you can switch to any tag, and create a > branch from there if you want to make changes to an older version. > > (Actually, you can switch to any commit you want and create a branch > from there : commits are kind of like ref-counted, and a tag is just > a named reference to a commit). > > However, if I missed something and there is something needed in these > branches, I can push them back. > > For tagging new releases, as we've discussed in previous messages, > it's all done from the "stable" branch : right now it contains the > 3.10.0 version, you can either commit directly to it or cherry-pick > commits from the master branch (i.e. just take specific commits > instead of the whole branch, if you want only the bugfixes to tag a > patch release, say 3.10.1). So the 'stable' branch is the last stable version. But, as far as I understand, I have no branch for the other stable versions. It is not really problematic, as usually we do fixes only in the current stable version. If someday we have to make a fix in 3.9, for example, we can just create a stable branch for 3.9 from its latest tag, and work on it. Do I get it correctly? > > You can also merge the master branch into stable, which will apply > all the commits the stable branch didn't have, in order to tag a new > release, say 3.11. OK, I see. > > Once you're done and the stable branch contains what you want to > release, you just have to create an annotated tag[0]. (Annotated tags > have checksums and can be signed, unlike simple tags which are just > pointers). And then it's done. :-) > > [0] https://git-scm.com/book/en/v2/Git-Basics-Tagging > OK. Now I have to understand how to deal with your merge request... -- Beno?t Minisini From gambas at ...1... Sat Aug 12 10:09:01 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 10:09:01 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: <22704d0c-fb06-57a1-a847-9ac7e1231fc5@...1...> References: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> <043b5e30-a62f-414c-98f9-66dce974e580@...1...> <7c2defaf-1b3f-7ab3-32b8-5ba96c3748b6@...1...> <2b80b59e-d0eb-9d6d-adb0-2b2507c32b94@...1...> <7fe2e6e3-5839-3c44-0f18-083d93a7416d@...1...> <22704d0c-fb06-57a1-a847-9ac7e1231fc5@...1...> Message-ID: Le 12/08/2017 ? 10:04, Beno?t Minisini a ?crit : > > Now I have to understand how to deal with your merge request... > OK, there is a fix for WITH I must check. But there is something about auto-completion that seems unrelated... Shouldn't you make two different merge requests? -- Beno?t Minisini From gambas at ...1... Sat Aug 12 10:45:14 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 10:45:14 +0200 Subject: [Gambas-devel] Another question about GitLab Message-ID: <2bb3e0cf-688f-a17f-d118-018836020bf9@...1...> Do I have to maintain the process of generating *.tar.gz source files and uploading them to SourceForge? Or can I just rely on the "download" button of GitLab, and its download URL? -- Beno?t Minisini From gambas at ...1... Sat Aug 12 10:49:21 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 10:49:21 +0200 Subject: [Gambas-devel] Change to gb.db.odbc to use ODBC Connection Strings. In-Reply-To: <562131C6.60604@...176...> References: <55DF51B8.6060706@...1...> <55F6EABB.4050804@...176...> <55F8B6BB.6070302@...1...> <55F97E63.5030603@...176...> <55F9889D.3080409@...1...> <55F9B7AF.6070403@...176...> <55F9C8D9.4030809@...1...> <1442840922852-53317.post@...752...> <5603427E.5090707@...1...> <56041E4F.8050806@...176...> <1444058739325-53761.post@...752...> <5612A588.3050001@...1...> <56180C59.2070501@...176...> <56181331.8020206@...1...> <5620FE1A.4040704@...176...> <56212524.5010105@...1...> <5621274A.5060605@...1...> <562131C6.60604@...176...> Message-ID: <8273e0ad-be94-7f61-90e5-e463568a2237@...1...> Le 16/10/2015 ? 19:20, ML a ?crit : > > Beno?t, > > Well, I was speaking about SQL-92 and the like... > > ODBC has a way to fetch a block of rows. You can set how many. Then, it > will retrieve (up to) that many rows from the rowset. > You can, IIRC, also specify the starting offset. All this, of course, as > long as the Driver or RDBM provides scrollable cursors. > Mind you, I never tried a row-block fetch, and it will be a demanding > 'challenge' to overcome. My guess is that it will take some time. > > Please tell me how can gb.db.odbc know whether someone used the > DB.Limit() property, so I can make the next fetch a row-block fetch, and > how to recognize a "go back to retrieving 1 row at a time" mode change. > Related to that, one of the things that still escape me is which calls > in gb.db map to which (block of) calls in gb.db.odbc. That, and which > high level Gambas calls map to which gb.db (block of) calls. > > Regards, > Hi, I just noticed I didn't deal with your mail... Do you have a GitLab account so that I can add you to the GitLab Gambas group? Do you have a real name that I can use? :-) Regards, -- Beno?t Minisini From adrien.prokopowicz at ...176... Sat Aug 12 11:36:13 2017 From: adrien.prokopowicz at ...176... (Adrien Prokopowicz) Date: Sat, 12 Aug 2017 11:36:13 +0200 Subject: [Gambas-devel] Gambas to Git(Lab) In-Reply-To: References: <4339edcf-09ce-fd46-8cd1-3bd1aed29864@...1...> <043b5e30-a62f-414c-98f9-66dce974e580@...1...> <7c2defaf-1b3f-7ab3-32b8-5ba96c3748b6@...1...> <2b80b59e-d0eb-9d6d-adb0-2b2507c32b94@...1...> <7fe2e6e3-5839-3c44-0f18-083d93a7416d@...1...> <22704d0c-fb06-57a1-a847-9ac7e1231fc5@...1...> Message-ID: Le Sat, 12 Aug 2017 10:09:01 +0200, Beno?t Minisini a ?crit: > Le 12/08/2017 ? 10:04, Beno?t Minisini a ?crit : >> Now I have to understand how to deal with your merge request... >> > > OK, there is a fix for WITH I must check. But there is something about > auto-completion that seems unrelated... Shouldn't you make two different > merge requests? > Yes sorry, I put the exclamation-mark completion work in another branch (I haven't made the Merge Request, because the first one needs to be merged first). There is still some completion changes, but these go along with the change in the compiler for nested WITHs. :-) Since you started working on the master branch, I disabled the automatic updates from SVN : because SVN has no idea about what's going on on Git, changes have to be manually merged instead of just fast-forwarded (I already merged #8175 into master). Also a small tip : in your account settings, you can also add your sourceforge email address to your account, this way the commits you made on SVN will be linked to your account instead of being from "another Beno?t". :-) -- Adrien Prokopowicz From adrien.prokopowicz at ...176... Sat Aug 12 11:43:53 2017 From: adrien.prokopowicz at ...176... (Adrien Prokopowicz) Date: Sat, 12 Aug 2017 11:43:53 +0200 Subject: [Gambas-devel] Another question about GitLab In-Reply-To: <2bb3e0cf-688f-a17f-d118-018836020bf9@...1...> References: <2bb3e0cf-688f-a17f-d118-018836020bf9@...1...> Message-ID: Le Sat, 12 Aug 2017 10:45:14 +0200, Beno?t Minisini via Gambas-devel a ?crit: > Do I have to maintain the process of generating *.tar.gz source files > and uploading them to SourceForge? > > Or can I just rely on the "download" button of GitLab, and its download > URL? > You definitely can. :-) That's actually how most hosted projects handle their downloads : they just hand over the GitLab or GitHub URL related to a specific tag. -- Adrien Prokopowicz From mckaygerhard at ...176... Sat Aug 12 16:36:07 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Sat, 12 Aug 2017 10:36:07 -0400 Subject: [Gambas-devel] Gambas to Git(Lab) Message-ID: Hi, the gambas git repository looks great! i want to share with yours the possibility of a mirror in github or other automatically (but not necesary): gitlab has a unique feature (well mostly a "lazy" feature), can automatically mirror and track changes to another repository.. the idea its to mantain a mirror git in github! .. i dont like so much due github are more close to non-free software.. and gitlab make more for freesoftware rather thant github.. the github mirror can be only a git repo without wiki and issue (github does not have the redirection features i suggested in gitlab) well great for the git change.. great job Benoit and Adrian.. and remenber that gitlab has many features in the "integration" and "services" tab of settings From gambas at ...1... Sat Aug 12 20:10:58 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 12 Aug 2017 20:10:58 +0200 Subject: [Gambas-devel] Switching to GitLab Message-ID: <3691541b-2d9a-0100-5a9a-3a5da6f8ab6f@...1...> Hi, The Gambas source repository is currently moving from SourceForge to GitLab. The Subversion repository is now read-only. The new git repository is at https://gitlab.com/gambas/gambas If you want a write access to the GitLab repository, sign in to GitLab and give me your account. The first 'gambas' is the name of the group of GitLab users. The second 'gambas' is the name of the project. Regards, -- Beno?t Minisini From mckaygerhard at ...176... Sun Aug 13 01:14:21 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Sat, 12 Aug 2017 19:14:21 -0400 Subject: [Gambas-devel] [Gambas-user] Switching to GitLab In-Reply-To: <3691541b-2d9a-0100-5a9a-3a5da6f8ab6f@...1...> References: <3691541b-2d9a-0100-5a9a-3a5da6f8ab6f@...1...> Message-ID: hi all, benoit. that's great news, long awaited, now I have more interest and expectations in the module odbc, my concern is that I cannot longer in future keep compiles "gambas" in my old linux .. I saw there that the openssl committee has been removed, after have been Need it on my embedded linux .. also was a great dessition not use github,and use gitlab, gitlab are more "free" software avocate rather thant github! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-08-12 14:10 GMT-04:00 Beno?t Minisini via Gambas-user : > Hi, > > The Gambas source repository is currently moving from SourceForge to GitLab. > > The Subversion repository is now read-only. > > The new git repository is at https://gitlab.com/gambas/gambas > > If you want a write access to the GitLab repository, sign in to GitLab and > give me your account. > > The first 'gambas' is the name of the group of GitLab users. > > The second 'gambas' is the name of the project. > > Regards, > > -- > Beno?t Minisini > > ------------------------------------------------------------------------------ > 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 From taboege at ...176... Sun Aug 13 01:18:59 2017 From: taboege at ...176... (Tobias Boege) Date: Sun, 13 Aug 2017 01:18:59 +0200 Subject: [Gambas-devel] [Gambas-user] Switching to GitLab In-Reply-To: References: <3691541b-2d9a-0100-5a9a-3a5da6f8ab6f@...1...> Message-ID: <20170812231859.GD541@...756...> On Sat, 12 Aug 2017, PICCORO McKAY Lenz wrote: > I saw there that the > openssl committee has been removed, after have been Need it on my > embedded linux .. > I haven't checked this but now that we're on git, you'll have an easy time maintaining your own fork for legacy-openssl Gambas and the commit should stay removed imho. Regards, Tobi -- "There's an old saying: Don't change anything... ever!" -- Mr. Monk From mckaygerhard at ...176... Sun Aug 13 06:47:58 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Sun, 13 Aug 2017 00:47:58 -0400 Subject: [Gambas-devel] Gambas to Git(Lab) Message-ID: 2017-08-12 3:49 GMT-04:00 : From: "Adrien Prokopowicz" >> Very strange: 3.10.0 tag is present in the "tags" section of the >> repository, but not when you pop down the list "switch branch/tag"... > > It's there, but the list isn't sorted in natural order, so it's right after > the 3.1.0 version. this its due 1.0 its minor rather than 10.0 to amek sense order must be 3.01.0 vs 3.10.0, i read the explanation of Adrian, very close to the subversion workflow.. i must added that in git all its technically "virtual" and the "commits" are always the point of work... unless the directory copy organization of subversion.. i make a equivalent git page of the http://gambaswiki.org/wiki/howto/svn as http://gambaswiki.org/wiki/howto/git with most close tho the svn but git are de-centralised so unless subversion, a commit its not a upload.. in git we can made many commits before made an upload.. so modify as prefer.. i only put info to compilation related > > I didn't push the branches for the stable versions, since the tags have the > same purpose : you can switch to any tag, and create a branch from there if > you want to make changes to an older version. > > (Actually, you can switch to any commit you want and create a branch from > there : > commits are kind of like ref-counted, and a tag is just a named reference > to a > commit). > > However, if I missed something and there is something needed in these > branches, > I can push them back. > > For tagging new releases, as we've discussed in previous messages, it's > all done > from the "stable" branch : right now it contains the 3.10.0 version, you > can either > commit directly to it or cherry-pick commits from the master branch (i.e. > just take > specific commits instead of the whole branch, if you want only the > bugfixes to tag > a patch release, say 3.10.1). > > You can also merge the master branch into stable, which will apply all the > commits the > stable branch didn't have, in order to tag a new release, say 3.11. > > Once you're done and the stable branch contains what you want to release, > you just > have to create an annotated tag[0]. (Annotated tags have checksums and can > be signed, > unlike simple tags which are just pointers). > And then it's done. :-) > > [0] https://git-scm.com/book/en/v2/Git-Basics-Tagging > > -- > Adrien Prokopowicz > > > > ------------------------------ > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Gambas-devel mailing list > Gambas-devel at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gambas-devel > > > ------------------------------ > > End of Gambas-devel Digest, Vol 113, Issue 2 > ******************************************** From mckaygerhard at ...176... Sun Aug 13 07:43:57 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Sun, 13 Aug 2017 01:43:57 -0400 Subject: [Gambas-devel] "should stay removed imho." ???? Message-ID: From: Tobias Boege > Message-ID: <20170812231859.GD541 at ...756...> > On Sat, 12 Aug 2017, PICCORO McKAY Lenz wrote: >> I saw there that the >> openssl committee has been removed, after have been Need it on my >> embedded linux .. > I haven't checked this but now that we're on git, you'll have an easy time > maintaining your own fork for legacy-openssl Gambas and the commit should > stay removed imho. > > Regards, > Tobi That's all! easy, no more No appeals, like a dictatorship ! After having accepted the change and even sent a patch and corroborated worked perfect? interesting! Support for 32-bit Motorola/IBM PowerPC (powerpc) has been removed in Stretch. So i must use for powerpc a older linux in debian, and pabkports package, i cannot "trash" the hardware due are working and perfectly! Spen 35$ on a Rasberry PI 3 B seem very cheap for you Tobi, but for us in Venezuela are VERY SPENSIVE, its a comlete lich for two persons.. so here many people that need make productive older environments withou changes need some effors and contributions, ahta that commit : https://sourceforge.net/p/gambas/code/7892/ was really need to use debian squeeze due its the most supported to run in the powerpc due recent debians and linuxes does not support I want to tell us something, in freetds, there's a sense on specific commit, support for older kernels.. why, simple connection to database direclty from embebed linuxes on mobile card computers.. that runs linux 2.6.18 will be great if Gambas can run in any environment witout making "magic" or need "hungry requeriments"... many countries does not like spend so much money on a "great software"... From adamnt42 at ...176... Sun Aug 13 08:08:47 2017 From: adamnt42 at ...176... (adamnt42 at ...176...) Date: Sun, 13 Aug 2017 15:38:47 +0930 Subject: [Gambas-devel] Sign me up please Message-ID: <20170813153847.918b78263baf4c7d45740a6b@...176...> Beno?t/Adrien, Could you please add me as a developer to the gitlab project. My GitLab id is "brucebruen ". Do you need anything else? I have a couple of things in the pipeline but don't have much free time at the moment, so little will happen for a while. The major contribution I am working on at the moment (when time allows) is an update to the autotools packager to comply with the new naming and destinations for Library projects. I have got it some way but am struggling with sed trying to derive the proper name for the package and library name and path... So I thought maybe I could branch off master and somebody with better sed skills (really, any sed skills would be better than mine) could help out. regards bruce -- B Bruen From mckaygerhard at ...176... Sun Aug 13 08:42:58 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Sun, 13 Aug 2017 02:42:58 -0400 Subject: [Gambas-devel] Change to gb.db.odbc to use ODBC Connection Strings. Message-ID: connection strings are since gabmas 3.7 ? this will break backguard compatiblity... about odbc and some bugs present, the multicursor fetch are a freedts limit, already reported and tested by me among others in freetds project contribution > Le 16/10/2015 ? 19:20, ML a ?crit : >> >> Beno?t, >> >> Well, I was speaking about SQL-92 and the like... >> >> ODBC has a way to fetch a block of rows. You can set how many. Then, it >> will retrieve (up to) that many rows from the rowset. >> You can, IIRC, also specify the starting offset. All this, of course, as >> long as the Driver or RDBM provides scrollable cursors. >> Mind you, I never tried a row-block fetch, and it will be a demanding >> 'challenge' to overcome. My guess is that it will take some time. >> >> Please tell me how can gb.db.odbc know whether someone used the >> DB.Limit() property, so I can make the next fetch a row-block fetch, and >> how to recognize a "go back to retrieving 1 row at a time" mode change. >> Related to that, one of the things that still escape me is which calls >> in gb.db map to which (block of) calls in gb.db.odbc. That, and which >> high level Gambas calls map to which gb.db (block of) calls. >> >> Regards, >> From adamnt42 at ...176... Sun Aug 13 10:14:48 2017 From: adamnt42 at ...176... (adamnt42 at ...176...) Date: Sun, 13 Aug 2017 17:44:48 +0930 Subject: [Gambas-devel] GitLab - some observations and questions Message-ID: <20170813174448.4a17a270f133ed82fb52d61b@...176...> I have had a reasonably good play with the GitLab repository over the last couple of days. So here's a few comments and questions. 1) I am pretty impressed with the Git/GitLab approach. I had an "experience" with Git a couple of years ago and hated it. The GitLab site makes it so much easier. So +++ 2) An item of concern (to me) is the appears to be no road map for moving Gambas to Git. As I said elsewhere, we are about to go into our busiest time of year and the thought of having to move my development system and our 6 sponsor clients to git in an unknown timeline scares me. As Adrien said somewhere in this list, there is still a lot to be done, it's not just a matter of moving the source. Documentation!!! How can I help? I can write wiki stuff in the evenings to wind down. When will the sourceforge repo disappear? Is there a disaster recovery plan (should, say, the GitLab repo get corrupted)? 3) I use modified versions of the IDE, several components and some of the mainline gambas code. The reasons for this are arcane, for example my gb.db.postgres is modified to take advantage of postgresql features not supported in other rdbms' and the mods are therefore philosophically at odds with the gambas gb.db common interface approach, so they won't be committed. Since we (here) design in and use postgres ONLY(! corporate rule :-) this is fine for us. To enable this, I have a local SVN repository cloned off the Sourceforge one and can adequately manage our differences with the eSVN tool. So, 3a) Can I run a local repository clone off the GitLab repo? If so, it looks like an even better approach than what we do now. I could envisage that we would have a close of "master" on our dev server with a main branch "local" where I can manage our differences. Then off that, I might have some other branches where I (me) can play with other changes while Felicity and my other developers can use a Gambas from "local"? Have I got the right idea? Is this feasible? 3b) Here's another example. I have a modified version of the FProperty class from the IDE that supports something I suggested a few years ago - "custom" property editors. There are two reasons why it was not committed to the Sourceforge repo. a) Beno?t did not like the idea at the time and b) I had to redesign most of the class code, mainly because I couldn't understand how the original works, which has resulted in a FProperty class that is completely different to the official one. SVN/eSVN handles this fairly easily as the file is marked "Replaced" and no merging or anything is required (until someone changes the official version for some reason! Given that the last change was rev 7730, I live in hope.) Can Git handle that situation? 3c) One shortcoming appears to me to be the way commits are identified. I mean it obviously works and that but I miss the SVN rev number which was sequential and relevant across all branches and most importantly was "human digestible". Looking at the recent GitLab commits, the revision id's appear to be things like "dcabf06c" ( Fabian's [GB.TERM.FORM] * NEW: New TermListBox widget.) Is there some logic to these random looking id's? 4) Commit comments!!! The SVN style was so easy to follow! Keep the standard! Can it be enforced in Git? That's enough for now, more later. (I'm busy trying to translate a certain wiki page.) Ah wait! One more! 5) Git clients. I have tried the following: * gitk - not bad * qgit - better * giggle - feature rich and functionally poor, but the best change browser of the three (and several CLI front ends). Any other suggestions (for managing my local clone) ? regards bruce -- B Bruen From adrien.prokopowicz at ...176... Sun Aug 13 12:38:55 2017 From: adrien.prokopowicz at ...176... (Adrien Prokopowicz) Date: Sun, 13 Aug 2017 12:38:55 +0200 Subject: [Gambas-devel] GitLab - some observations and questions In-Reply-To: <20170813174448.4a17a270f133ed82fb52d61b@...176...> References: <20170813174448.4a17a270f133ed82fb52d61b@...176...> Message-ID: Le Sun, 13 Aug 2017 10:14:48 +0200, adamnt42 at ...176... a ?crit: > I have had a reasonably good play with the GitLab repository over the > last couple of days. So here's a few comments and questions. > > 1) I am pretty impressed with the Git/GitLab approach. I had an > "experience" with Git a couple of years ago and hated it. The GitLab > site makes it so much easier. So +++ > 2) An item of concern (to me) is the appears to be no road map for > moving Gambas to Git. As I said elsewhere, we are about to go into our > busiest time of year and the thought of having to move my development > system and our 6 sponsor clients to git in an unknown timeline scares > me. As Adrien said somewhere in this list, there is still a lot to be > done, it's not just a matter of moving the source. Documentation!!! How > can I help? I can write wiki stuff in the evenings to wind down. Indeed, we need a proper "How To Git" page on the wiki, that explains the following : - How to get the source from the repo (git clone, this one is easy) - How to contribute (for external developers) : forking the repo, the commit log format, staying up-to-date, creating merge requests, etc. > When will the sourceforge repo disappear? As Beno?t said, the sourceforge repo is just read-only, and I don't think it will be ever deleted (unless SourceForge goes down, of course). > Is there a disaster recovery plan (should, say, the GitLab repo get > corrupted)? I don't think there ever was a proper disaster recovery plan with SourceForge either, but the nature of Git makes it so everyone having a copy of the repo also have the full history of the branch(es) they're on, so we can push it elsewhere if needed. (Actually, it's possible to make a clone without the full history using the --depth=1 argument when cloning, but the default is to get the full history). > 3) I use modified versions of the IDE, several components and some of > the mainline gambas code. The reasons for this are arcane, for example > my gb.db.postgres is modified to take advantage of postgresql features > not supported in other rdbms' and the mods are therefore philosophically > at odds with the gambas gb.db common interface approach, so they won't > be committed. Since we (here) design in and use postgres ONLY(! > corporate rule :-) this is fine for us. To enable this, I have a local > SVN repository cloned off the Sourceforge one and can adequately manage > our differences with the eSVN tool. So, > 3a) Can I run a local repository clone off the GitLab repo? If so, it > looks like an even better approach than what we do now. I could > envisage that we would have a close of "master" on our dev server with > a main branch "local" where I can manage our differences. Then off > that, I might have some other branches where I (me) can play with other > changes while Felicity and my other developers can use a Gambas from > "local"? Have I got the right idea? Is this feasible? You can definitely do this, on your own server, but GitLab supports it too. :) In GitLab, on the repository's page, you can click the "Fork" button. It will create a copy of the Gambas repository to your account. You can then clone this repository on your machine and push any commits you want, it will only affect your copy. In order to stay up-to-date with the main repository, you will have to merge the original master branch into your own. To do this, you can add a second (read-only) remote to your local copy, using this command : git remote add upstream https://gitlab.com/gambas/gambas.git I called the remote "upstream" here, but you can call it as you want. (You can also use SSH, I just put the HTTPS here because credentials are not required to use it). Then, when you are on your master branch, you can ask git to merge the master branch from the original repository this way : git pull upstream master It then works like a regular merge, you only have to do this from time to time whenever you want to update your Gambas version. If you do not want to do this using GitLab but on one of your own servers instead, you will first have to set up a bare (i.e. empty) Git repository on your server : https://git-scm.com/book/it/v2/Git-on-the-Server-Setting-Up-the-Server When it is done, use the local copy of the Gambas repo you (may have) already cloned, and add an origin that points to your server, using regular SSH : git remote add bruceserver git at ...770...:wherever/is/your/repo/gambas.git Then you can clone it, and add the original repo as a remote just like above with GitLab. This actually is common practice in OSS projects (except for the self-hosted version), so this will certainly end up in the contributing guide on the wiki. > 3b) Here's another example. I have a modified version of the FProperty > class from the IDE that supports something I suggested a few years ago - > "custom" property editors. There are two reasons why it was not > committed to the Sourceforge repo. a) Beno?t did not like the idea at > the time and b) I had to redesign most of the class code, mainly because > I couldn't understand how the original works, which has resulted in a > FProperty class that is completely different to the official one. > SVN/eSVN handles this fairly easily as the file is marked "Replaced" and > no merging or anything is required (until someone changes the official > version for some reason! Given that the last change was rev 7730, I live > in hope.) Can Git handle that situation? From my experience, Git handles very well 90% of the merges. For completely different files however, it will stop halfway through the merge, and mark some files as "conflicting". You can then use the `git mergetool` command, which will walk you through each conflicting file using your favorite diff program (I personally use KDiff3, but it supports many more). When done, you just commit your changes, and it's merged and ready to push. > 3c) One shortcoming appears to me to be the way commits are identified. > I mean it obviously works and that but I miss the SVN rev number which > was sequential and relevant across all branches and most importantly was > "human digestible". Looking at the recent GitLab commits, the revision > id's appear to be things like "dcabf06c" ( Fabian's [GB.TERM.FORM] * > NEW: New TermListBox widget.) Is there some logic to these random > looking id's? What you have here is the "short" commit ID (which is enough 99% of the time). The full ID is actually this : dcabf06cbf725137810408ed7c10c167b6863956. The logic behind those ids is basically "please don't collide". Because Git is decentralized in nature (see the above examples of across-origins merges and commits), you cannot have both a sequential and unique revision number. This is even the case on a single repository : if users A and B both commit to their local repositories, since Git doesn't know about each other's changes (until they get pushed and pulled), it cannot just do rev+1 like SVN does (you can think of Git as peer-to-peer, while SVN is just client/server). However, you can use `git rev-list --count HEAD` to count the number of commits since the beginning. This number is not reliable for representing a specific commit, but it can vaguely tell you how behind you are from recent changes. GitLab also creates a small visual representation of "x commits behind / x commits ahead" on its branch list page (https://gitlab.com/gambas/gambas/branches), which can be useful too. > 4) Commit comments!!! The SVN style was so easy to follow! Keep the > standard! Can it be enforced in Git? The commit comment style is actually a format enforced by Beno?t, it has nothing to do with SVN. I actually like it a lot, and I have already used it in a number of other Git projects. I only apply a small change to it : I use the first line as a short description of what the commit is, before adding the full changelog. This is because all Git tools show the first line as a short commit description (like here : https://gitlab.com/gambas/gambas/commits/master), and just having the first section tag is unhelpful at best. Since Beno?t's standard ignores non-prefixed lines, it doesn't matter and is skipped when making the final revision changelog. :) > Ah wait! One more! > 5) Git clients. I have tried the following: > * gitk - not bad > * qgit - better > * giggle - feature rich and functionally poor, but the best change > browser of the three > (and several CLI front ends). > Any other suggestions (for managing my local clone) ? This is my personal opinion, but I have not found a single standalone git client on linux that I like (especially for viewing changes before committing). Oddly enough, I like the Git tools integrated in IDEs much better. I've used QtCreator, NetBeans, The JetBrains IDEs and probably others I forgot. So for now I use mostly the command line, but in KDE I also use the small Git integration plugin for Dolphin, and with a small ZSH integration that shows the Git current branch & working copy status in my prompt. I am currently prototyping a Gambas component that interfaces with libgit2, so we can have a proper integration within the IDE, and why not make a Gambas git graphical client in the future. :-) -- Adrien Prokopowicz From d4t4full at ...176... Sun Aug 13 15:02:41 2017 From: d4t4full at ...176... (d4t4full at ...176...) Date: Sun, 13 Aug 2017 10:02:41 -0300 Subject: [Gambas-devel] [Gambas-user] Switching to GitLab In-Reply-To: References: <3691541b-2d9a-0100-5a9a-3a5da6f8ab6f@...1...> Message-ID: <9b5ff133-4e14-4a1e-9a2d-0ddaa63181d0@...176...> +1 TIA zxMarce On Aug 13, 2017, 09:57, at 09:57, Gianluigi wrote: >Hi Benoit, > >I apologize for ignorance but I have never used Git. >To update the Trunk, what should I do now? >To subscribe to the new ML? >To report a bug? >Write access is only for participating in the code, or? > >Regards >Gianluigi > >2017-08-12 20:10 GMT+02:00 Beno?t Minisini via Gambas-user < >gambas-user at lists.sourceforge.net>: > >> Hi, >> >> The Gambas source repository is currently moving from SourceForge to >> GitLab. >> >> The Subversion repository is now read-only. >> >> The new git repository is at https://gitlab.com/gambas/gambas >> >> If you want a write access to the GitLab repository, sign in to >GitLab and >> give me your account. >> >> The first 'gambas' is the name of the group of GitLab users. >> >> The second 'gambas' is the name of the project. >> >> Regards, >> >> -- >> Beno?t Minisini >> >> ------------------------------------------------------------ >> ------------------ >> 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 >> >------------------------------------------------------------------------------ >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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From adamnt42 at ...176... Sun Aug 13 16:30:51 2017 From: adamnt42 at ...176... (adamnt42 at ...176...) Date: Mon, 14 Aug 2017 00:00:51 +0930 Subject: [Gambas-devel] GitLab - some observations and questions In-Reply-To: References: <20170813174448.4a17a270f133ed82fb52d61b@...176...> Message-ID: <20170814000051.4d8ccb9ae419ed27cbd8c70d@...176...> Thanks for that info Adrien, you have cleared up a lot of what I thought but could not confirm to my own satisfaction from reading/playing. To save you having to wade through the below here are a few comments (referenced to my original points). 2) I agree and would like to help with the How To. (I tried to "translate" Piccoro's well intentioned draft page but got lost.) I am currently drafting a set of wiki pages locally (using Olivier Cruille' s most excellent markdown editor from the farm!) I feel we may need two pages (at least) one for contributors and one for non-contributing users. There is just too much to write for each one for a single page and it might be confusing for the latter to be subjected to the workflows, updates etc etc. Your thoughts? 2) Regarding the r/o status of the sourceforge repository. Ah I see, so I guess I'll just limit us to "emergency patching" for now. 2) DRP. Ok, that makes me a lot more confident! 3) and 3a) (Local clone) Thank you very much for that info - much clearer now! 3b) I am still not sure whether I am happy about the loss of the "replaced" status from SVN. :-( I guess I'll just wait and see). P.S. I generally use diffuse, which I have managed to integrate with most of the GUI client's I've tried so that is some pain killer I suppose. 3c) revision ID's : ah now I get it! I guess I'll get used to it. 4) comments (snip pasted from below) > This is because all Git tools show the first line as a short commit description > (like here : https://gitlab.com/gambas/gambas/commits/master), and just > having the first section tag is unhelpful at best. > Since Beno?t's standard ignores non-prefixed lines, it doesn't matter and > is skipped when making the final revision changelog. :) Hmmmmmm. My experience is converse. I like to see what "area" a change affects as a summary and the details I can review in the fullness of time. For example, a change to [GB.JIT] is not going to worry me too much as we don;t use it. (There are reasons.) But a change to [GB.DB] or [GB.DB.POSTGRES] will affect us so I want to review that asap. How about a compromise? Put the section tag and a short description on the first line. P.S. I thought that the SVN could enforce the commit comments because some years ago I set up a little "template" in esvn to "enforce" it - I just forgot all about that. I see some of the clients seem to have a similar feature, I look at them some time. 5) (clients) Yes. they all do seem to be strong in some areas and &#$^&# weak in others. Giggle, for example is great at browsing the change history but lousy at managing commits, etc. Just thought someone might have found the "magic" answer. 5) (gambas IDE integration) Love to help! With some reservations I know my way around the IDE pretty well. Let me know when your component is usable. (Actually I really should focus on that autotools packaging fix though.) Thanks again. bruce On Sun, 13 Aug 2017 12:38:55 +0200 "Adrien Prokopowicz" wrote: > Le Sun, 13 Aug 2017 10:14:48 +0200, adamnt42 at ...176... > a ?crit: > > > I have had a reasonably good play with the GitLab repository over the > > last couple of days. So here's a few comments and questions. > > > > 1) I am pretty impressed with the Git/GitLab approach. I had an > > "experience" with Git a couple of years ago and hated it. The GitLab > > site makes it so much easier. So +++ > > 2) An item of concern (to me) is the appears to be no road map for > > moving Gambas to Git. As I said elsewhere, we are about to go into our > > busiest time of year and the thought of having to move my development > > system and our 6 sponsor clients to git in an unknown timeline scares > > me. As Adrien said somewhere in this list, there is still a lot to be > > done, it's not just a matter of moving the source. Documentation!!! How > > can I help? I can write wiki stuff in the evenings to wind down. > > Indeed, we need a proper "How To Git" page on the wiki, that explains the > following : > - How to get the source from the repo (git clone, this one is easy) > - How to contribute (for external developers) : forking the repo, the > commit log > format, staying up-to-date, creating merge requests, etc. > > > When will the sourceforge repo disappear? > > As Beno?t said, the sourceforge repo is just read-only, and I don't think > it will > be ever deleted (unless SourceForge goes down, of course). > > > Is there a disaster recovery plan (should, say, the GitLab repo get > > corrupted)? > > I don't think there ever was a proper disaster recovery plan with > SourceForge either, > but the nature of Git makes it so everyone having a copy of the repo also > have the > full history of the branch(es) they're on, so we can push it elsewhere if > needed. > > (Actually, it's possible to make a clone without the full history using the > --depth=1 argument when cloning, but the default is to get the full > history). > > > 3) I use modified versions of the IDE, several components and some of > > the mainline gambas code. The reasons for this are arcane, for example > > my gb.db.postgres is modified to take advantage of postgresql features > > not supported in other rdbms' and the mods are therefore philosophically > > at odds with the gambas gb.db common interface approach, so they won't > > be committed. Since we (here) design in and use postgres ONLY(! > > corporate rule :-) this is fine for us. To enable this, I have a local > > SVN repository cloned off the Sourceforge one and can adequately manage > > our differences with the eSVN tool. So, > > 3a) Can I run a local repository clone off the GitLab repo? If so, it > > looks like an even better approach than what we do now. I could > > envisage that we would have a close of "master" on our dev server with > > a main branch "local" where I can manage our differences. Then off > > that, I might have some other branches where I (me) can play with other > > changes while Felicity and my other developers can use a Gambas from > > "local"? Have I got the right idea? Is this feasible? > > You can definitely do this, on your own server, but GitLab supports it > too. :) > > In GitLab, on the repository's page, you can click the "Fork" button. > It will create a copy of the Gambas repository to your account. You can > then > clone this repository on your machine and push any commits you want, it > will > only affect your copy. > > In order to stay up-to-date with the main repository, you will have to > merge > the original master branch into your own. To do this, you can add a second > (read-only) remote to your local copy, using this command : > > git remote add upstream https://gitlab.com/gambas/gambas.git > > I called the remote "upstream" here, but you can call it as you want. > (You can also use SSH, I just put the HTTPS here because credentials are > not > required to use it). > > Then, when you are on your master branch, you can ask git to merge the > master > branch from the original repository this way : > > git pull upstream master > > It then works like a regular merge, you only have to do this from time to > time > whenever you want to update your Gambas version. > > If you do not want to do this using GitLab but on one of your own servers > instead, > you will first have to set up a bare (i.e. empty) Git repository on your > server : > > https://git-scm.com/book/it/v2/Git-on-the-Server-Setting-Up-the-Server > > When it is done, use the local copy of the Gambas repo you (may have) > already > cloned, and add an origin that points to your server, using regular SSH : > > git remote add bruceserver > git at ...770...:wherever/is/your/repo/gambas.git > > Then you can clone it, and add the original repo as a remote just like > above with > GitLab. > > This actually is common practice in OSS projects (except for the > self-hosted version), > so this will certainly end up in the contributing guide on the wiki. > > > 3b) Here's another example. I have a modified version of the FProperty > > class from the IDE that supports something I suggested a few years ago - > > "custom" property editors. There are two reasons why it was not > > committed to the Sourceforge repo. a) Beno?t did not like the idea at > > the time and b) I had to redesign most of the class code, mainly because > > I couldn't understand how the original works, which has resulted in a > > FProperty class that is completely different to the official one. > > SVN/eSVN handles this fairly easily as the file is marked "Replaced" and > > no merging or anything is required (until someone changes the official > > version for some reason! Given that the last change was rev 7730, I live > > in hope.) Can Git handle that situation? > > From my experience, Git handles very well 90% of the merges. For completely > different files however, it will stop halfway through the merge, and mark > some files as "conflicting". You can then use the `git mergetool` command, > which will walk you through each conflicting file using your favorite diff > program > (I personally use KDiff3, but it supports many more). > When done, you just commit your changes, and it's merged and ready to push. > > > 3c) One shortcoming appears to me to be the way commits are identified. > > I mean it obviously works and that but I miss the SVN rev number which > > was sequential and relevant across all branches and most importantly was > > "human digestible". Looking at the recent GitLab commits, the revision > > id's appear to be things like "dcabf06c" ( Fabian's [GB.TERM.FORM] * > > NEW: New TermListBox widget.) Is there some logic to these random > > looking id's? > > What you have here is the "short" commit ID (which is enough 99% of the > time). > The full ID is actually this : dcabf06cbf725137810408ed7c10c167b6863956. > > The logic behind those ids is basically "please don't collide". Because > Git is > decentralized in nature (see the above examples of across-origins merges > and commits), > you cannot have both a sequential and unique revision number. > > This is even the case on a single repository : if users A and B both > commit to their > local repositories, since Git doesn't know about each other's changes > (until they get > pushed and pulled), it cannot just do rev+1 like SVN does (you can think > of Git as > peer-to-peer, while SVN is just client/server). > > However, you can use `git rev-list --count HEAD` to count the number of > commits since > the beginning. This number is not reliable for representing a specific > commit, but it > can vaguely tell you how behind you are from recent changes. > GitLab also creates a small visual representation of "x commits behind / x > commits > ahead" on its branch list page > (https://gitlab.com/gambas/gambas/branches), which can > be useful too. > > > 4) Commit comments!!! The SVN style was so easy to follow! Keep the > > standard! Can it be enforced in Git? > > The commit comment style is actually a format enforced by Beno?t, it has > nothing to > do with SVN. > I actually like it a lot, and I have already used it in a number of other > Git projects. > I only apply a small change to it : I use the first line as a short > description of what > the commit is, before adding the full changelog. > > This is because all Git tools show the first line as a short commit > description > (like here : https://gitlab.com/gambas/gambas/commits/master), and just > having the first > section tag is unhelpful at best. > Since Beno?t's standard ignores non-prefixed lines, it doesn't matter and > is skipped when > making the final revision changelog. :) > > > Ah wait! One more! > > 5) Git clients. I have tried the following: > > * gitk - not bad > > * qgit - better > > * giggle - feature rich and functionally poor, but the best change > > browser of the three > > (and several CLI front ends). > > Any other suggestions (for managing my local clone) ? > > This is my personal opinion, but I have not found a single standalone git > client > on linux that I like (especially for viewing changes before committing). > Oddly enough, > I like the Git tools integrated in IDEs much better. I've used QtCreator, > NetBeans, > The JetBrains IDEs and probably others I forgot. > > So for now I use mostly the command line, but in KDE I also use the small > Git > integration plugin for Dolphin, and with a small ZSH integration that shows > the Git current branch & working copy status in my prompt. > > I am currently prototyping a Gambas component that interfaces with > libgit2, so we > can have a proper integration within the IDE, and why not make a Gambas git > graphical client in the future. :-) > > -- > 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-devel mailing list > Gambas-devel at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gambas-devel -- B Bruen From mckaygerhard at ...176... Sun Aug 13 17:12:24 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Sun, 13 Aug 2017 11:12:24 -0400 Subject: [Gambas-devel] GitLab - some observations and questions In-Reply-To: <20170813174448.4a17a270f133ed82fb52d61b@...176...> References: <20170813174448.4a17a270f133ed82fb52d61b@...176...> Message-ID: 2017-08-13 4:14 GMT-04:00 adamnt42 at ...176... : > 1) I am pretty impressed with the Git/GitLab approach. I had an "experience" with Git a couple of > years ago and hated it. The GitLab site makes it so much easier. So +++ gitlab interface its the most feature rich! unfortunatelly there's no good gui client like rapidsvn for git counterpart > 2) An item of concern (to me) is the appears to be no road map for moving Gambas to Git. Yeah maybe the roadmap was a feature Initiative and i think its not so "critical" git (as i see from you) are more flexible rather than subversion.. > Documentation!!! How can I help? I can write wiki stuff in the evenings to wind down. http://gambaswiki.org/wiki/doc/markdown#t9 very consencus and clear, there's more but for start its enought until When will the sourceforge repo disappear? Is there a disaster recovery plan (should, say, the GitLab repo get corrupted)? > 3) I use modified versions of the IDE, several components and some of the mainline gambas code. > The reasons for this are arcane, for example my gb.db.postgres is modified to take advantage of > postgresql features not supported in other rdbms' and the mods are therefore philosophically at odds > with the gambas gb.db common interface approach, so they won't be committed. Since we (here) > design in and use postgres ONLY(! corporate rule :-) this is fine for us. I'm very interesting on your local patches.. > To enable this, I have a local SVN repository cloned off the Sourceforge one and can adequately in gitlab with a simple button called "fork" you can track the repository and now best: with a simple configuration, that fork can update automatically, and your changes can be in a specific branch, inclusivelly you can made this into the main repository and gambas developers can take advantage of your changes! > 3a) Can I run a local repository clone off the GitLab repo? yeah, please take a read : http://gambaswiki.org/wiki/howto/git#t3 > Then off that, I might have some other branches where I (me) can play with other changes while Felicity and my other developers can use a Gambas from "local"? Have I got the right idea? Is this feasible? Please take in consideration that in git branches are "virtual references" > 3b) Here's another example. I have a modified version of the FProperty class from the IDE that supports something I suggested a few years ago - "custom" property editors. There are two reasons why it was not committed to the Sourceforge repo. a) Beno?t did not like the idea at the time and b) I had to redesign most of the class code, mainly because I couldn't understand how the original works, which has resulted in a FProperty class that is completely different to the official one. SVN/eSVN handles this fairly easily as the file is marked "Replaced" and no merging or anything is required (until someone changes the official version for some reason! Given that the last change was rev 7730, I live in hope.) Can Git handle that situation? can use the "Fork" button. o inclusive make a local git BARE copy and upload as original a fork its like a copy but with author change... and for AUTOMATIC update to your repository use the integrate tab of thesettings. to track use branches.. and mantain original branches to manage differences.. also the original master branch into your own a add a second remote to your local copy, using this command git remote add upstream https://gitlab.com/gambas/gambas.git thas are also writable but only in your copy.. From mckaygerhard at ...176... Mon Aug 14 21:01:42 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Mon, 14 Aug 2017 15:01:42 -0400 Subject: [Gambas-devel] SVN->GIT log format Message-ID: reading the svn wiki and viewing the subversion repository i now understantd a important organization piece : the commit log! in git there's two operations that does not conform the LOG format .. the sync/merge local and the sync/pull merge remote so a new log format must (i think) define for this king of "commits" in the repository, see it!: 'Merge branch 'master' of gitlab.com:gambas/gambas' in the commit https://gitlab.com/gambas/gambas/commit/2343dd7899c74a1314e05d06495de15a55160b2d does not follow the log format... also the pull merge and merge request must also be in same format for external contribution to follow old log in wiki Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com From adrien.prokopowicz at ...176... Mon Aug 14 21:11:26 2017 From: adrien.prokopowicz at ...176... (Adrien Prokopowicz) Date: Mon, 14 Aug 2017 21:11:26 +0200 Subject: [Gambas-devel] SVN->GIT log format In-Reply-To: References: Message-ID: Le Mon, 14 Aug 2017 21:01:42 +0200, PICCORO McKAY Lenz a ?crit: > reading the svn wiki and viewing the subversion repository i now > understantd a important organization piece : the commit log! > > in git there's two operations that does not conform the LOG format .. > the sync/merge local and the sync/pull merge remote > > so a new log format must (i think) define for this king of "commits" > in the repository, see it!: > > 'Merge branch 'master' of gitlab.com:gambas/gambas' > > in the commit > https://gitlab.com/gambas/gambas/commit/2343dd7899c74a1314e05d06495de15a55160b2d > > does not follow the log format... also the pull merge and merge > request must also be in same format for external contribution to > follow old log in wiki > > Lenz McKAY Gerardo (PICCORO) > http://qgqlochekone.blogspot.com From my understanding, the commit log format is only used to make the Release Changelog. Everything that doesn't start with the tags will just get ignored. Which is the right thing to do for merge commits. :-) -- Adrien Prokopowicz From mckaygerhard at ...176... Mon Aug 14 21:19:09 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Mon, 14 Aug 2017 15:19:09 -0400 Subject: [Gambas-devel] SVN->GIT log format In-Reply-To: References: Message-ID: ahh! ok.. thanks for clarify! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-08-14 15:11 GMT-04:00 Adrien Prokopowicz : > Le Mon, 14 Aug 2017 21:01:42 +0200, PICCORO McKAY Lenz > a ?crit: > >> reading the svn wiki and viewing the subversion repository i now >> understantd a important organization piece : the commit log! >> >> in git there's two operations that does not conform the LOG format .. >> the sync/merge local and the sync/pull merge remote >> >> so a new log format must (i think) define for this king of "commits" >> in the repository, see it!: >> >> 'Merge branch 'master' of gitlab.com:gambas/gambas' >> >> in the commit >> https://gitlab.com/gambas/gambas/commit/2343dd7899c74a1314e05d06495de15a55160b2d >> >> does not follow the log format... also the pull merge and merge >> request must also be in same format for external contribution to >> follow old log in wiki >> >> Lenz McKAY Gerardo (PICCORO) >> http://qgqlochekone.blogspot.com > > > From my understanding, the commit log format is only used to make the > Release Changelog. > Everything that doesn't start with the tags will just get ignored. Which is > the right > thing to do for merge commits. :-) > > -- > 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-devel mailing list > Gambas-devel at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gambas-devel From bastiangermann at ...754... Tue Aug 15 11:45:28 2017 From: bastiangermann at ...754... (Bastian Germann) Date: Tue, 15 Aug 2017 11:45:28 +0200 Subject: [Gambas-devel] gambas-cygport git project Message-ID: <77588165-dec2-74bf-be2b-fa15ede9adf1@...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 From mckaygerhard at ...176... Tue Aug 15 16:11:08 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Tue, 15 Aug 2017 10:11:08 -0400 Subject: [Gambas-devel] gambas-cygport git project In-Reply-To: <77588165-dec2-74bf-be2b-fa15ede9adf1@...754...> References: <77588165-dec2-74bf-be2b-fa15ede9adf1@...754...> Message-ID: 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 : > 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 From bastiangermann at ...754... Tue Aug 15 18:06:40 2017 From: bastiangermann at ...754... (Bastian Germann) Date: Tue, 15 Aug 2017 18:06:40 +0200 Subject: [Gambas-devel] gambas-cygport git project In-Reply-To: References: <77588165-dec2-74bf-be2b-fa15ede9adf1@...754...> Message-ID: <9a9d1b8a-35ab-37eb-ce2f-8059551f8184@...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 : >> 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 From mckaygerhard at ...176... Tue Aug 15 20:57:24 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Tue, 15 Aug 2017 14:57:24 -0400 Subject: [Gambas-devel] gambas-cygport git project In-Reply-To: <9a9d1b8a-35ab-37eb-ce2f-8059551f8184@...754...> References: <77588165-dec2-74bf-be2b-fa15ede9adf1@...754...> <9a9d1b8a-35ab-37eb-ce2f-8059551f8184@...754...> Message-ID: 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 : > 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 : >>> 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 From bastiangermann at ...754... Tue Aug 15 21:18:07 2017 From: bastiangermann at ...754... (Bastian Germann) Date: Tue, 15 Aug 2017 21:18:07 +0200 Subject: [Gambas-devel] gambas-cygport git project In-Reply-To: References: <77588165-dec2-74bf-be2b-fa15ede9adf1@...754...> <9a9d1b8a-35ab-37eb-ce2f-8059551f8184@...754...> Message-ID: 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 : >> 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 : >>>> 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 From mckaygerhard at ...176... Tue Aug 15 21:20:24 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Tue, 15 Aug 2017 15:20:24 -0400 Subject: [Gambas-devel] gambas-cygport git project In-Reply-To: References: <77588165-dec2-74bf-be2b-fa15ede9adf1@...754...> <9a9d1b8a-35ab-37eb-ce2f-8059551f8184@...754...> Message-ID: 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 : > 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 : >>> 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 : >>>>> 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 From d4t4full at ...176... Fri Aug 18 02:26:26 2017 From: d4t4full at ...176... (zxMarce) Date: Thu, 17 Aug 2017 17:26:26 -0700 (MST) Subject: [Gambas-devel] Cannot populate database Connection.Name from ODBC driver. Message-ID: <1503015986177-60002.post@...752...> Hi there. This is mainly intended to be tackled by Beno?t, but anyone with the necessary knowledge (Toby?) please feel free to butt in. The ODBC driver can use Connection Strings since some time now. I also have a patched up module that can run successfully non-data-producing queries (the SQL_NO_DATA return code is no longer treated as an error), thanks to a bug submitted by Piccoro. Problem is in the open_database() function. When using connstrings, the database name is usually part of this string, and no .Name property is expected to be populated from the BASIC program, nor actually used. So, I'm trying to populate the property from the ODBC backend. I can successfully fetch the DB Name from the lower level database driver in use (SQLite3 does not provide a name, tho, be warned). What I cannot do, be it via copying char[] or Gambas String buffer pointers, is to get the .Name property populated back to the running BASIC program. The open_database() call has two parameters: DB_DESC *desc and DB_DATABASE *db. My best guess is that I have to fiddle with desc, but not really sure if that's correct nor exactly how. To further salt the issue, queries exist in big RDBMS that allow to hot-switch databases while connected to a server (example: USE in MSSQL). So, the connection's .Name property should also be "refetched" after a successful query is run. Any suggestions? -- View this message in context: http://gambas.8142.n7.nabble.com/Cannot-populate-database-Connection-Name-from-ODBC-driver-tp60002.html Sent from the gambas-devel mailing list archive at Nabble.com. From adamnt42 at ...176... Fri Aug 18 03:11:51 2017 From: adamnt42 at ...176... (adamnt42 at ...176...) Date: Fri, 18 Aug 2017 10:41:51 +0930 Subject: [Gambas-devel] Cannot populate database Connection.Name from ODBC driver. In-Reply-To: <1503015986177-60002.post@...752...> References: <1503015986177-60002.post@...752...> Message-ID: <20170818104151.b2b606209a3bc409a243e594@...176...> On Thu, 17 Aug 2017 17:26:26 -0700 (MST) zxMarce wrote: > (SQLite3 does not provide a name, tho, be warned). Isn't a sqlite db without a name an "in memory" database? b -- B Bruen From adamnt42 at ...176... Fri Aug 18 03:21:13 2017 From: adamnt42 at ...176... (adamnt42 at ...176...) Date: Fri, 18 Aug 2017 10:51:13 +0930 Subject: [Gambas-devel] Git - more surprises Message-ID: <20170818105113.4094818899998cccb4eeb872@...176...> Ok, so I did the pull into our local "gambasbase" clone which is a "single-branch" of the "master". All worked fine and super quick. Then, I did a pull from my personal clone of "gambasbase". This one has some branches in it for our (paddys-hill) changes. That pull automagically started a merge, which is fine, but then.... it invoked vim on the commit header. That was a surprise! Not the least of which was trying to remember how the heck to get out of vim. Is there a way to turn off this "feature"? b -- B Bruen From gambas at ...1... Fri Aug 18 03:25:20 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Fri, 18 Aug 2017 03:25:20 +0200 Subject: [Gambas-devel] Cannot populate database Connection.Name from ODBC driver. In-Reply-To: <1503015986177-60002.post@...752...> References: <1503015986177-60002.post@...752...> Message-ID: <1e8bb6c3-d115-c9ed-664a-ecf4ff0848a0@...1...> Le 18/08/2017 ? 02:26, zxMarce a ?crit : > Hi there. This is mainly intended to be tackled by Beno?t, but anyone with > the necessary knowledge (Toby?) please feel free to butt in. > > The ODBC driver can use Connection Strings since some time now. I also have > a patched up module that can run successfully non-data-producing queries > (the SQL_NO_DATA return code is no longer treated as an error), thanks to a > bug submitted by Piccoro. > > Problem is in the open_database() function. When using connstrings, the > database name is usually part of this string, and no .Name property is > expected to be populated from the BASIC program, nor actually used. > So, I'm trying to populate the property from the ODBC backend. I can > successfully fetch the DB Name from the lower level database driver in use > (SQLite3 does not provide a name, tho, be warned). > What I cannot do, be it via copying char[] or Gambas String buffer pointers, > is to get the .Name property populated back to the running BASIC program. > > The open_database() call has two parameters: DB_DESC *desc and DB_DATABASE > *db. My best guess is that I have to fiddle with desc, but not really sure > if that's correct nor exactly how. > > To further salt the issue, queries exist in big RDBMS that allow to > hot-switch databases while connected to a server (example: USE > in MSSQL). So, the connection's .Name property should also be "refetched" > after a successful query is run. > > Any suggestions? > > The open_database(DB_DESC *desc, DB_DATABASE *db) driver function takes two arguments: - DB_DESC *desc : a pointer to a structure that contains all connections string properties and an integer option field. - DB_DATABASE *db : a pointer to another structure that should be filled with all necessary information about the connection. By modifying the desc fields, you are modifying the corresponding Connection object properties, as this is where they are stored. But you must use GB.FreeString() and GB.NewString() to replace a string property value. For example: const char *new_value; GB.FreeString(&desc->name); // Free the Gambas string containing the old database name desc->name = GB.NewZeroString(new_value); // Create a new Gambas string from the zero-terminated string new_value, and store it. That's it. -- Beno?t Minisini From gambas at ...1... Fri Aug 18 03:26:29 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Fri, 18 Aug 2017 03:26:29 +0200 Subject: [Gambas-devel] Git - more surprises In-Reply-To: <20170818105113.4094818899998cccb4eeb872@...176...> References: <20170818105113.4094818899998cccb4eeb872@...176...> Message-ID: <4d3f4983-e09d-e6c2-7a3c-623258d9383c@...1...> Le 18/08/2017 ? 03:21, adamnt42 at ...176... a ?crit : > Ok, so I did the pull into our local "gambasbase" clone which is a "single-branch" of the "master". All worked fine and super quick. > > Then, I did a pull from my personal clone of "gambasbase". This one has some branches in it for our (paddys-hill) changes. That pull automagically started a merge, which is fine, but then.... > > it invoked vim on the commit header. That was a surprise! Not the least of which was trying to remember how the heck to get out of vim. > > Is there a way to turn off this "feature"? > > b > Check your EDITOR environment variable. I put "kwrite" in it, and everything went fine. -- Beno?t Minisini From adamnt42 at ...176... Fri Aug 18 03:30:40 2017 From: adamnt42 at ...176... (adamnt42 at ...176...) Date: Fri, 18 Aug 2017 11:00:40 +0930 Subject: [Gambas-devel] Git - a helpful tutorial Message-ID: <20170818110040.1cb6af726d75b4a089afd24e@...176...> https://www.atlassian.com/git/tutorials/svn-to-git-prepping-your-team-migration#for-developers I found that page especially the "for developers" bit, and indeed that whole site, very helpful in understanding what is actually going on. hth b -- B Bruen From adamnt42 at ...176... Fri Aug 18 03:35:21 2017 From: adamnt42 at ...176... (adamnt42 at ...176...) Date: Fri, 18 Aug 2017 11:05:21 +0930 Subject: [Gambas-devel] GitLab - notifications Message-ID: <20170818110521.8e2fd5d0f912066bea3b473e@...176...> I've read the help and thought I had notifications set up properly for gambas/gambas, but nothing ever shows up. The only way I found that there are some new changes was from discussions in this list. I get notifications via email from my own GitLab playground, but not from gambas/gambas. Is there some magical incantation I need to perform? tia b -- B Bruen From adrien.prokopowicz at ...176... Fri Aug 18 03:54:10 2017 From: adrien.prokopowicz at ...176... (Adrien Prokopowicz) Date: Fri, 18 Aug 2017 03:54:10 +0200 Subject: [Gambas-devel] GitLab - notifications In-Reply-To: <20170818110521.8e2fd5d0f912066bea3b473e@...176...> References: <20170818110521.8e2fd5d0f912066bea3b473e@...176...> Message-ID: Le Fri, 18 Aug 2017 03:35:21 +0200, adamnt42 at ...176... a ?crit: > I've read the help and thought I had notifications set up properly for > gambas/gambas, but nothing ever shows up. The only way I found that > there are some new changes was from discussions in this list. > I get notifications via email from my own GitLab playground, but not > from gambas/gambas. > Is there some magical incantation I need to perform? > > tia > b > The global "Watch" settings for the Gambas group works for me, but personally I've been using the RSS feed to avoid being flooded with emails : https://gitlab.com/gambas.atom It's available on the "Activity" tab of the Gambas group. -- Adrien Prokopowicz From lordheavym at ...176... Fri Aug 18 08:14:16 2017 From: lordheavym at ...176... (Laurent Carlier) Date: Fri, 18 Aug 2017 08:14:16 +0200 Subject: [Gambas-devel] Git - a helpful tutorial In-Reply-To: <20170818110040.1cb6af726d75b4a089afd24e@...176...> References: <20170818110040.1cb6af726d75b4a089afd24e@...176...> Message-ID: <1674902.gjkfGoaKQH@...772...> Le vendredi 18 ao?t 2017, 03:30:40 CEST adamnt42 at ...176... a ?crit : > https://www.atlassian.com/git/tutorials/svn-to-git-prepping-your-team-migrat > ion#for-developers > > I found that page especially the "for developers" bit, and indeed that whole > site, very helpful in understanding what is actually going on. > > hth > b And what about an officia l book? https://git-scm.com/book/en/v2 and available in various languages. -- Laurent Carlier http://www.archlinux.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: This is a digitally signed message part. URL: From mckaygerhard at ...176... Fri Aug 18 09:22:15 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Fri, 18 Aug 2017 03:22:15 -0400 Subject: [Gambas-devel] GitLab - notifications In-Reply-To: <20170818110521.8e2fd5d0f912066bea3b473e@...176...> References: <20170818110521.8e2fd5d0f912066bea3b473e@...176...> Message-ID: there are levels of "whatching".. the default its only notify if something are relevat and related to you.. but its you arenot mention or an isue are not mentioned or related to you.. there's no notification that's the default.. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-08-17 21:35 GMT-04:00 adamnt42 at ...176... : > I've read the help and thought I had notifications set up properly for gambas/gambas, but nothing ever shows up. The only way I found that there are some new changes was from discussions in this list. > I get notifications via email from my own GitLab playground, but not from gambas/gambas. > Is there some magical incantation I need to perform? > > tia > b > > -- > B Bruen > > ------------------------------------------------------------------------------ > 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 From mckaygerhard at ...176... Fri Aug 18 09:37:04 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Fri, 18 Aug 2017 03:37:04 -0400 Subject: [Gambas-devel] Cannot populate database Connection.Name from ODBC driver. In-Reply-To: <1e8bb6c3-d115-c9ed-664a-ecf4ff0848a0@...1...> References: <1503015986177-60002.post@...752...> <1e8bb6c3-d115-c9ed-664a-ecf4ff0848a0@...1...> Message-ID: hi zxMarce and other, i want to mark a WARNING here.. as i can see too many experience with mososoft SQL and must be some notes about some other scalar HIGH DBMS.. sybase DOES NOT NEED A DB NAME TO HAVE A CONNECTION ! be warning: its not like sqlite that a db "in memory" are present at least, here theres no connection, in same way db2 and oracle... 2017-08-17 21:25 GMT-04:00 Beno?t Minisini via Gambas-devel : > const char *new_value; > > GB.FreeString(&desc->name); // Free the Gambas string containing the old > database name > > desc->name = GB.NewZeroString(new_value); // Create a new Gambas string from > the zero-terminated string new_value, and store it. its great that can be changed the connection db on the fly for the module.. its mandatory.. ok ODBC need! a connection db name when Established, but its only with UnixODBC.. there's more "special behaviours" * in same "host connection name" there are also "same many db names" that its not the same as "in same host are many db names served" that strange behaviour are applied to oralce and sybase, that runs "a instance" of the software for "one or more than" databases... in the same host.. due that PROPIETARY ODBC SOFTWARE CAN OFFERS A CONNECTION TO GAMBAS WITHOUT A DATABASE VALID STRUCTURE, or a "empty valid connection" in conclusion.. or more rare as succed to me, a connection but the db are not the spected (due UnixODBC freedts can connect to a one db per host at same time, as all here knowed. but it not limited to in real ysbae or oracle) > > That's it. > > -- > Beno?t Minisini > > > ------------------------------------------------------------------------------ > 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 From d4t4full at ...176... Fri Aug 18 13:22:34 2017 From: d4t4full at ...176... (ML) Date: Fri, 18 Aug 2017 08:22:34 -0300 Subject: [Gambas-devel] Cannot populate database Connection.Name from ODBC driver. In-Reply-To: References: <1503015986177-60002.post@...752...> <1e8bb6c3-d115-c9ed-664a-ecf4ff0848a0@...1...> Message-ID: <9d380fb7-eaa0-d7ed-7c4c-aea8d967d847@...176...> Beno?t, Thanks a ton. It looks way easier than I tried/thought... As usual. Piccoro, First off, I always default my examples to MSSQL because I work with them, for good or bad. That's mainly what I have to try/test things from Gambas. But a single MySQL server -which is mostly free ($$$) IIRC- can also be home to more than one DB/Catalog. Others may or may not follow suit. Never tried Sybase, DB/2, or Oracle because I don't have access to either. I rely on users to report inconsistencies like I had for Firebird regarding RecordCount. Never mind RDBMS that don't have a DB Name. The interface should be as wide/general as possible, and if at least one of them uses or can switch DB/Catalog names, then I think it should be supported. Actually, SQLite3 (the one I do have at home, with your supplied example of "CREATE IF NOT EXIST Tabla1...") fails to retrieve at least the DB filename (test.sq3) as the Database/Catalog name. That particular DB is a file, so I guess the driver should retrieve *something* as DB Name but it does not, confusing everybody into thinking it's an in-memory DB. On the other hand, connstrings handle instances -at least with MSSQL- transparently by specifying the instance in the server name, and this is separate from the DB name. So you can have any mix-n-match of servers, instances, and DBs, given every server/instance has its own connection object. Then you can switch DBs/Catalogs inside each Connection by running MSSQL's USE (or the applicable RDBMS-specific) query command. Regards, zxMarce. On 18/08/17 04:37, PICCORO McKAY Lenz wrote: > hi zxMarce and other, i want to mark a WARNING here.. as i can see too > many experience with mososoft SQL and must be some notes about some > other scalar HIGH DBMS.. > sybase DOES NOT NEED A DB NAME TO HAVE A CONNECTION ! > be warning: its not like sqlite that a db "in memory" are present at > least, here theres no connection, in same way db2 and oracle... > > 2017-08-17 21:25 GMT-04:00 Beno?t Minisini via Gambas-devel > : >> const char *new_value; >> GB.FreeString(&desc->name); // Free the Gambas string containing the >> old database name >> desc->name = GB.NewZeroString(new_value); // Create a new Gambas >> string from the zero-terminated string new_value, and store it. > its great that can be changed the connection db on the fly for the > module.. its mandatory.. > ok ODBC need! a connection db name when Established, but its only with > UnixODBC.. there's more "special behaviours" in same "host connection > name" there are also "same many db names" that its not the same as "in > same host are many db names served" > that strange behaviour are applied to oralce and sybase, that runs "a > instance" of the software for "one or more than" databases... in the > same host.. > due that PROPIETARY ODBC SOFTWARE CAN OFFERS A CONNECTION TO GAMBAS > WITHOUT A DATABASE VALID STRUCTURE, or a "empty valid connection" in > conclusion.. or more rare as succed to me, a connection but the db are > not the spected (due UnixODBC freedts can connect to a one db per host > at same time, as all here knowed. but it not limited to in real ysbae > or oracle) >> That's it. >> -- >> Beno?t Minisini From mckaygerhard at ...176... Fri Aug 18 14:39:27 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Fri, 18 Aug 2017 08:39:27 -0400 Subject: [Gambas-devel] Cannot populate database Connection.Name from ODBC driver. In-Reply-To: <9d380fb7-eaa0-d7ed-7c4c-aea8d967d847@...176...> References: <1503015986177-60002.post@...752...> <1e8bb6c3-d115-c9ed-664a-ecf4ff0848a0@...1...> <9d380fb7-eaa0-d7ed-7c4c-aea8d967d847@...176...> Message-ID: 2017-08-18 7:22 GMT-04:00 ML : > of "CREATE IF NOT EXIST Tabla1...") fails to retrieve at least the DB > filename (test.sq3) as the Database/Catalog name. > That particular DB is a file, so I guess the driver should retrieve > *something* as DB Name but it does not, confusing everybody into that's the behaviour that i try to explain... DBMS connection "intance" dont have to handle a db "instance" that's behaviour its copied from M$ in mysql and postgres but DBMS in the connections dont must handle a db "instance" and that's correct... but ODBC M$ especifications said that must.. this king of "rare" conflicts its common in documents where M$ are involved! -------------- next part -------------- An HTML attachment was scrubbed... URL: From gambas at ...1... Fri Aug 18 14:51:20 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Fri, 18 Aug 2017 14:51:20 +0200 Subject: [Gambas-devel] Cannot populate database Connection.Name from ODBC driver. In-Reply-To: References: <1503015986177-60002.post@...752...> <1e8bb6c3-d115-c9ed-664a-ecf4ff0848a0@...1...> <9d380fb7-eaa0-d7ed-7c4c-aea8d967d847@...176...> Message-ID: <4945d547-1718-9da5-31cc-6d1f988b1759@...1...> Le 18/08/2017 ? 14:39, PICCORO McKAY Lenz a ?crit : > > that's the behaviour that i try to explain... DBMS connection "intance" > dont have to handle a db "instance" that's behaviour its copied from M$ > in mysql and postgres but DBMS in the connections dont must handle a db > "instance" and that's correct... but ODBC M$ especifications said that > must.. this king of "rare" conflicts its common in documents where M$ > are involved! > I have no idea what you try to tell us, your english is absolutely unreadable. Please try to make some effort! Can't you, at least, install an english spelling checker on your mail client or your browser? It would be a good start. As for the grammar, I don't know if there is a grammatical corrector for english on Linux. Regards, -- Beno?t Minisini From mckaygerhard at ...176... Fri Aug 18 17:14:15 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Fri, 18 Aug 2017 11:14:15 -0400 Subject: [Gambas-devel] Cannot populate database Connection.Name from ODBC driver. In-Reply-To: <4945d547-1718-9da5-31cc-6d1f988b1759@...1...> References: <1503015986177-60002.post@...752...> <1e8bb6c3-d115-c9ed-664a-ecf4ff0848a0@...1...> <9d380fb7-eaa0-d7ed-7c4c-aea8d967d847@...176...> <4945d547-1718-9da5-31cc-6d1f988b1759@...1...> Message-ID: umm okok, write in the browser event in the console: 2017-08-18 7:22 GMT-04:01 ML : > of "CREATE IF NOT EXIST Tabla1...") fails to retrieve at least the DB > filename (test.sq3) as the Database/Catalog name. > That particular DB is a file, so I guess the driver should retrieve > *something* as DB Name but it does not, confusing everybody into that's the behaviour that i try to explain... a DBMS connection "instance" don't have to handle a db "instance", that's behaviour found on DBMS's such like postgres or mysql inherits from the "M$" era but are not mandatory... but in many propietary DBMS the connections dont "must handle" a db "instance" and that's correct... in some place the ODBC especification said that a db name must be provided, but mayor DBMS dont need a db name provided, that's behaviour are found commonly in Oracle, Firebird, Sybase, SAP and many other, almost all the propietary DBMS do in this way... Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-08-18 8:51 GMT-04:00 Beno?t Minisini : > Le 18/08/2017 ? 14:39, PICCORO McKAY Lenz a ?crit : > >> >> that's the behaviour that i try to explain... DBMS connection "intance" >> dont have to handle a db "instance" that's behaviour its copied from M$ in >> mysql and postgres but DBMS in the connections dont must handle a db >> "instance" and that's correct... but ODBC M$ especifications said that >> must.. this king of "rare" conflicts its common in documents where M$ are >> involved! >> >> > I have no idea what you try to tell us, your english is absolutely > unreadable. > > Please try to make some effort! > > Can't you, at least, install an english spelling checker on your mail > client or your browser? It would be a good start. > > As for the grammar, I don't know if there is a grammatical corrector for > english on Linux. > > Regards, > > -- > Beno?t Minisini > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisml at ...757... Fri Aug 18 22:31:03 2017 From: chrisml at ...757... (Christof Thalhofer) Date: Fri, 18 Aug 2017 22:31:03 +0200 Subject: [Gambas-devel] Git - more surprises In-Reply-To: <4d3f4983-e09d-e6c2-7a3c-623258d9383c@...1...> References: <20170818105113.4094818899998cccb4eeb872@...176...> <4d3f4983-e09d-e6c2-7a3c-623258d9383c@...1...> Message-ID: <4772f539-45b3-5fb4-ec5a-34681e33ed50@...757...> Am 18.08.2017 um 03:26 schrieb Beno?t Minisini via Gambas-devel: > Check your EDITOR environment variable. I put "kwrite" in it, and > everything went fine. This can be done also for Git (global or per repository) only: https://stackoverflow.com/questions/2596805/how-do-i-make-git-use-the-editor-of-my-choice-for-commits Alles Gute Christof Thalhofer -- Dies ist keine Signatur -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From d4t4full at ...176... Mon Aug 21 00:34:37 2017 From: d4t4full at ...176... (First Last) Date: Sun, 20 Aug 2017 19:34:37 -0300 Subject: [Gambas-devel] Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? Message-ID: Guy, grew a pair and did the following: Got my account (zxMarce) at GitLab. Created and added the necessary SSH Keys. Then, cloned with "git clone https://gitlab.com/gambas/gambas.git gambasdevel". Navigated to "gb.db.odbc/src" and changed the old "main.c" with my changed file from ye olde SF SVN tree (kept changes by bgermann from 3 days ago). Then, I guessed I had to commit my changes to my local repo, so I tried "git commit". But Git surprised me by asking my for name and email (wow! heavier than the NSA!). I supplied my GitLab username and email, then tried to commit again, but could not due to changes not staged (?!). The exchange was thus: ~/gambasdevel$ git commit *** Please tell me who you are. Run git config --global user.email "you at ...773..." git config --global user.name "Your Name" to set your account's default identity. Omit --global to set the identity only in this repository. fatal: unable to auto-detect email address (got 'xxx at ...774...') ~/gambasdevel$ git config --global user.email "d4t4full at ...176..." ~/gambasdevel$ git config --global user.name "zxMarce" ~/gambasdevel$ git commit On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: modified: gb.db.odbc/src/main.c Untracked files: gb.db.odbc/src/ml_doit.sh no changes added to commit The untracked .sh is a script I made myself to quickly compile and install the ODBC component. It should remain so. But I don't know how to "stage" and then "commit" my changed file. Then, I will have to deal with change-logging and uploading, but I'd like to go "baby steps". TIA, zxMarce. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mckaygerhard at ...176... Mon Aug 21 02:36:29 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Sun, 20 Aug 2017 20:36:29 -0400 Subject: [Gambas-devel] Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: References: Message-ID: you forgot the "git add gb.db.odbc/src/main.c" before git commit its like the commit in git are to "mark what be uploaded to repository" so then: git clone https://gitlab.com/gambas/gambas.git gambasdevel cd gambasdevel git config --global user.email "zxarce-email" git config --global user.name "zxMarce" editor gb.db.odbc/src/main.c git add gb.db.odbc/src/main.c git commit -m "[gb.odbc] solve situation of odbc, to the great piccoro that really need this artgggg" git push this are in conclusion.. if have any other comment please feel free to mail me.. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-08-20 18:34 GMT-04:00 First Last : > Guy, grew a pair and did the following: Got my account (zxMarce) at > GitLab. Created and added the necessary SSH Keys. > > Then, cloned with "git clone https://gitlab.com/gambas/gambas.git > gambasdevel". > Navigated to "gb.db.odbc/src" and changed the old "main.c" with my changed > file from ye olde SF SVN tree (kept changes by bgermann from 3 days ago). > > Then, I guessed I had to commit my changes to my local repo, so I tried > "git commit". But Git surprised me by asking my for name and email (wow! > heavier than the NSA!). I supplied my GitLab username and email, then tried > to commit again, but could not due to changes not staged (?!). The exchange > was thus: > > ~/gambasdevel$ git commit > > *** Please tell me who you are. > > Run > > git config --global user.email "you at ...773..." > git config --global user.name "Your Name" > > to set your account's default identity. > Omit --global to set the identity only in this repository. > > fatal: unable to auto-detect email address (got 'xxx at ...774...') > ~/gambasdevel$ git config --global user.email "d4t4full at ...176..." > ~/gambasdevel$ git config --global user.name "zxMarce" > ~/gambasdevel$ git commit > On branch master > Your branch is up-to-date with 'origin/master'. > Changes not staged for commit: > modified: gb.db.odbc/src/main.c > > Untracked files: > gb.db.odbc/src/ml_doit.sh > > no changes added to commit > > The untracked .sh is a script I made myself to quickly compile and install > the ODBC component. It should remain so. > But I don't know how to "stage" and then "commit" my changed file. > Then, I will have to deal with change-logging and uploading, but I'd like > to go "baby steps". > > TIA, > zxMarce. > > ------------------------------------------------------------ > ------------------ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From d4t4full at ...176... Mon Aug 21 05:29:50 2017 From: d4t4full at ...176... (First Last) Date: Mon, 21 Aug 2017 00:29:50 -0300 Subject: [Gambas-devel] Fwd: Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: References: Message-ID: Ok, no luck. Looks like I have to be authorized first (which sounds reasonable), but don't know who to ask for auth. This is the output I got for GIT PUSH: Username for 'https://gitlab.com': zxMarce Password for 'https://zxMarce at ...775...': remote: HTTP Basic: Access denied fatal: Authentication failed for 'https://gitlab.com/gambas/gambas.git/' So, cannot upload today. When someone sees this maybe I get the green light. Regards, zxMarce. On Sun, Aug 20, 2017 at 9:36 PM, PICCORO McKAY Lenz wrote: > you forgot the "git add gb.db.odbc/src/main.c" before git commit > > its like the commit in git are to "mark what be uploaded to repository" > > so then: > > git clone https://gitlab.com/gambas/gambas.git gambasdevel > cd gambasdevel > git config --global user.email "zxarce-email" > git config --global user.name "zxMarce" > editor gb.db.odbc/src/main.c > git add gb.db.odbc/src/main.c > git commit -m "[gb.odbc] solve situation of odbc, to the great piccoro > that really need this artgggg" > git push > > this are in conclusion.. if have any other comment please feel free to > mail me.. > > > Lenz McKAY Gerardo (PICCORO) > http://qgqlochekone.blogspot.com > > 2017-08-20 18:34 GMT-04:00 First Last : > >> Guys, grew a pair and did the following: Got my account (zxMarce) at >> GitLab. Created and added the necessary SSH Keys. >> >> Then, cloned with "git clone https://gitlab.com/gambas/gambas.git >> gambasdevel". >> Navigated to "gb.db.odbc/src" and changed the old "main.c" with my >> changed file from ye olde SF SVN tree (kept changes by bgermann from 3 days >> ago). >> >> Then, I guessed I had to commit my changes to my local repo, so I tried >> "git commit". But Git surprised me by asking my for name and email (wow! >> heavier than the NSA!). I supplied my GitLab username and email, then tried >> to commit again, but could not due to changes not staged (?!). The exchange >> was thus: >> >> ~/gambasdevel$ git commit >> >> *** Please tell me who you are. >> >> Run >> >> git config --global user.email "you at ...773..." >> git config --global user.name "Your Name" >> >> to set your account's default identity. >> Omit --global to set the identity only in this repository. >> >> fatal: unable to auto-detect email address (got 'xxx at ...774...') >> ~/gambasdevel$ git config --global user.email "d4t4full at ...176..." >> ~/gambasdevel$ git config --global user.name "zxMarce" >> ~/gambasdevel$ git commit >> On branch master >> Your branch is up-to-date with 'origin/master'. >> Changes not staged for commit: >> modified: gb.db.odbc/src/main.c >> >> Untracked files: >> gb.db.odbc/src/ml_doit.sh >> >> no changes added to commit >> >> The untracked .sh is a script I made myself to quickly compile and >> install the ODBC component. It should remain so. >> But I don't know how to "stage" and then "commit" my changed file. >> Then, I will have to deal with change-logging and uploading, but I'd like >> to go "baby steps". >> >> TIA, >> zxMarce. >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From adamnt42 at ...176... Mon Aug 21 08:25:29 2017 From: adamnt42 at ...176... (adamnt42 at ...176...) Date: Mon, 21 Aug 2017 15:55:29 +0930 Subject: [Gambas-devel] Fwd: Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: References: Message-ID: <20170821155529.13165eb627dd492e50e717f8@...176...> Try something along the lines of this $ $ cd [your local repository] <1> $ git add * <2> $ git commit -a -s <3> $ git format-patch master <4> $ git send-email --to=" " 00*.patch <5> This is what is known colloquially as a "git WorkFlow". In other words it's all the stuff that needs to be done to make some "other stuff" happen. The bits are explanations of what is happening here. Don't type them. The [?] bits are needed see below. As in use the IDE, whatever, to make your changes. Try them out, fix, etc, etc. This is not really a command line but is part of what you do "every-day", so to speak. Nor is it anything to do with git. <1> OK, so the fix is looking good. Now we want to get into "git" mode. (This was the hardest thing I had to come to terms with. git is actually just a "source code manager" aka "SCM". Some may wish to call it a "VCS" (Version Control Manager) which it is - if and only if you are the administrator of the pure source base. If you are as old as I am perhaps the following may jog some memories "PCVS", "PVCS", etc.) "git", as in your locally installed "git" only works at the command line level with the current working directory, i.e. what you get with $ pwd So, [your local repository] is the directory where you cloned the original gambas source down to. We are now somewhere where "git" commands can be used. <2> This is only "really" necessary if you have added any new files to your local repository. File deletions and modifications to existing files are taken care of automagically in the following. You could also use $ git add [my new file] to tell git about a specific new file, but "git add *" does take care of any of those little things we may have forgotten. And by the way it doesn't do any damage. If there are no new files then it will tell you so. If there are some then it will tell you that anyway. So, where are we at now. In short, "git" now knows that there is new "stuff" in your local repository. This "stuff" is in the files that EXIST in your local repository. In other words, if you were to open one of those files in a text editor, then what you would see is the file exactly as you left it. BUT we now have to start thinking in "git" mode. ... How can I state this. ... ah, bugger political correctness. "git" is like your 16 year old son who can't find his football boots on Saturday morning, but he is "sure" they "should" be exactly where he left them last Saturday afternoon (i.e. in the middle of the laundry floor). So we have to tell him, "No, I cleaned them, polished them and put them back in your cupboard last Sunday." Likewise, we have to tell "git" the same type of thing. Hey "git", your boots are back in the supboard! This is called a "commit". So now we know what it is we will <3> Then make a commit to your local repository. -a means that all (sorry, ALL) your local changes will be committed to your local repository. -s means that the commit will be signed with your (local or "global" email name and address) So, now the "son", sorry the "git" now knows that you are serious. In it's tiny little mind it compares it's idea of what the file should look like to what it actually looks like and comes up with a set of "differences". Sort of like "son" comparing his mental image of the laundry floor and the actual contents of the cupboard... thinks "Hmm, that's strange, the laundry fairies must have moved them?" Which is why the -s is kind of important. <4> Woops! I gotta go do stuff. I'll finish this ;ater. b -- B Bruen From mckaygerhard at ...176... Mon Aug 21 08:35:40 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Mon, 21 Aug 2017 02:35:40 -0400 Subject: [Gambas-devel] Fwd: Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: <20170821155529.13165eb627dd492e50e717f8@...176...> References: <20170821155529.13165eb627dd492e50e717f8@...176...> Message-ID: too many words.. zxMarce has only one problem.. dont have access to git repository .. Benoit must added it.. (later) and then he can commit normally the alternate way its the cited workflow, lest resume: 1. fork the repo to your account: zxMarce (will be then at https://gitlab.com/zxMarce/gambas.git/) 2. clone: git clone https://gitlab.com/zxMarce/gambas.git gambasdevel 3. cd gambasdevel 4. edit gb.db/odbc/gb.db.odbc/src/main.c 5. git commit -a 6. git push 7. then now in gitlab interface made a pull request to the gambas repo Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-08-21 2:25 GMT-04:00 adamnt42 at ...176... : > Try something along the lines of this > > $ > $ cd [your local repository] <1> > $ git add * <2> > $ git commit -a -s <3> > $ git format-patch master <4> > $ git send-email --to=" " 00*.patch <5> > > This is what is known colloquially as a "git WorkFlow". In other words > it's all the stuff that needs to be done to make some "other stuff" happen. > > The bits are explanations of what is happening here. Don't type them. > The [?] bits are needed see below. > > As in use the IDE, whatever, to make your changes. Try > them out, fix, etc, etc. This is not really a command line but is part of > what you do "every-day", so to speak. Nor is it anything to do with git. > > <1> OK, so the fix is looking good. Now we want to get into "git" mode. > (This was the hardest thing I had to come to terms with. git is actually > just a "source code manager" aka "SCM". Some may wish to call it a "VCS" > (Version Control Manager) which it is - if and only if you are the > administrator of the pure source base. If you are as old as I am perhaps > the following may jog some memories "PCVS", "PVCS", etc.) "git", as in your > locally installed "git" only works at the command line level with the > current working directory, i.e. what you get with $ pwd > So, > [your local repository] is the directory where you cloned the original > gambas source down to. > We are now somewhere where "git" commands can be used. > > <2> This is only "really" necessary if you have added any new files to > your local repository. File deletions and modifications to existing files > are taken care of automagically in the following. You could also use $ git > add [my new file] to tell git about a specific new file, but "git add *" > does take care of any of those little things we may have forgotten. And by > the way it doesn't do any damage. If there are no new files then it will > tell you so. If there are some then it will tell you that anyway. > > So, where are we at now. In short, "git" now knows that there is new > "stuff" in your local repository. This "stuff" is in the files that EXIST > in your local repository. In other words, if you were to open one of those > files in a text editor, then what you would see is the file exactly as you > left it. BUT we now have to start thinking in "git" mode. ... > > How can I state this. ... ah, bugger political correctness. > "git" is like your 16 year old son who can't find his football boots on > Saturday morning, but he is "sure" they "should" be exactly where he left > them last Saturday afternoon (i.e. in the middle of the laundry floor). > So we have to tell him, "No, I cleaned them, polished them and put them > back in your cupboard last Sunday." > Likewise, we have to tell "git" the same type of thing. Hey "git", your > boots are back in the supboard! > This is called a "commit". > So now we know what it is we will > > <3> Then make a commit to your local repository. > -a means that all (sorry, ALL) your local changes will be > committed to your local repository. > -s means that the commit will be signed with your (local or > "global" email name and address) > > So, now the "son", sorry the "git" now knows that you are serious. In it's > tiny little mind it compares it's idea of what the file should look like to > what it actually looks like and comes up with a set of "differences". Sort > of like "son" comparing his mental image of the laundry floor and the > actual contents of the cupboard... thinks "Hmm, that's strange, the laundry > fairies must have moved them?" > Which is why the -s is kind of important. > > <4> > > Woops! I gotta go do stuff. > I'll finish this ;ater. > > b > -- > B Bruen > > ------------------------------------------------------------ > ------------------ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien.prokopowicz at ...176... Mon Aug 21 08:43:38 2017 From: adrien.prokopowicz at ...176... (Adrien Prokopowicz) Date: Mon, 21 Aug 2017 08:43:38 +0200 Subject: [Gambas-devel] Fwd: Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: References: <20170821155529.13165eb627dd492e50e717f8@...176...> Message-ID: Le Mon, 21 Aug 2017 08:35:40 +0200, PICCORO McKAY Lenz a ?crit: > too many words.. > zxMarce has only one problem.. dont have access to git repository .. > Benoit must added it.. (later) and then he can commit normally > > the alternate way its the cited workflow, lest resume: > fork the repo to your account: zxMarce (will be then at > https://gitlab.com/zxMarce/gambas.git/) > clone: git clone https://gitlab.com/zxMarce/gambas.git gambasdevel > cd gambasdevel > edit gb.db/odbc/gb.db.odbc/src/main.c > git commit -a > git push > then now in gitlab interface made a pull request to the gambas repo Everyone who wants to contribute shouldn't have write access to the repository ! The fork / merge request workflow is how you should contribute (not an "alternate way"), if everybody had write access it would be quite a mess ! I am writing a "how to contribute" guide that will be uploaded to the wiki right now, explaining in detail how to use Git and GitLab to make contributions without having write access to the main repository. -- Adrien Prokopowicz -------------- next part -------------- An HTML attachment was scrubbed... URL: From mckaygerhard at ...176... Mon Aug 21 09:11:10 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Mon, 21 Aug 2017 03:11:10 -0400 Subject: [Gambas-devel] Fwd: Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: References: <20170821155529.13165eb627dd492e50e717f8@...176...> Message-ID: Adrien the "CONTRIBUTE" file also must be at the git repository, as all the git repository suggest.. please added to that! the "alternate" was due the transition from SVN Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-08-21 2:43 GMT-04:00 Adrien Prokopowicz : > Le Mon, 21 Aug 2017 08:35:40 +0200, PICCORO McKAY Lenz < > mckaygerhard at ...176...> a ?crit: > > too many words.. > > zxMarce has only one problem.. dont have access to git repository .. > > Benoit must added it.. (later) and then he can commit normally > > the alternate way its the cited workflow, lest resume: > > 1. fork the repo to your account: zxMarce (will be then at > https://gitlab.com/zxMarce/gambas.git/) > 2. clone: git clone https://gitlab.com/zxMarce/gambas.git gambasdevel > 3. cd gambasdevel > 4. edit gb.db/odbc/gb.db.odbc/src/main.c > 5. git commit -a > 6. git push > 7. then now in gitlab interface made a pull request to the gambas repo > > Everyone who wants to contribute shouldn't have write access to the > repository ! > > The fork / merge request workflow is how you should contribute (not an > "alternate > way"), if everybody had write access it would be quite a mess ! > > I am writing a "how to contribute" guide that will be uploaded to the wiki > right > now, explaining in detail how to use Git and GitLab to make contributions > without > having write access to the main repository. > > -- > 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-devel mailing list > Gambas-devel at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gambas-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From adamnt42 at ...176... Mon Aug 21 10:48:35 2017 From: adamnt42 at ...176... (adamnt42 at ...176...) Date: Mon, 21 Aug 2017 18:18:35 +0930 Subject: [Gambas-devel] Fwd: Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: References: <20170821155529.13165eb627dd492e50e717f8@...176...> Message-ID: <20170821181835.ddaf7cd07cc30b0d139fc72e@...176...> On Mon, 21 Aug 2017 02:35:40 -0400 PICCORO McKAY Lenz wrote: > too many words.. > > zxMarce has only one problem.. dont have access to git repository .. > No, picorro, you don't understand. YOU Have much experience with git. WE don't. Look at it from the other side of the fence! -- B Bruen From d4t4full at ...176... Mon Aug 21 17:02:33 2017 From: d4t4full at ...176... (d4t4full at ...176...) Date: Mon, 21 Aug 2017 12:02:33 -0300 Subject: [Gambas-devel] Fwd: Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: <20170821155529.13165eb627dd492e50e717f8@...176...> References: <20170821155529.13165eb627dd492e50e717f8@...176...> Message-ID: <25c6e0fa-4fc4-4a50-9497-721bd6e3c5c9@...176...> Bruce, Thanks a bunch for taking the little time you had to explain things. Funny and educational! So, looking some further mails it looks like THIS is THE WAY to submit. Since I'm new to Git, I'll hold for part II of your instructions. I wonder, though, if I broke anything by doing what I already did. Nevermind, I'll clone again (after I save the code I modded). I also wonder why I had to GIT ADD a file that was cloned, tho. Shouldn't Git already know the file WAS modded and that it HAD to be committed? Anyway I didn't commit it signed so I clearly messed up. Regards, zxMarce. On Aug 21, 2017, 03:25, at 03:25, "adamnt42 at ...176..." wrote: >Try something along the lines of this > > $ > $ cd [your local repository] <1> > $ git add * <2> > $ git commit -a -s <3> > $ git format-patch master <4> > $ git send-email --to=" " 00*.patch <5> > >This is what is known colloquially as a "git WorkFlow". In other words >it's all the stuff that needs to be done to make some "other stuff" >happen. > >The bits are explanations of what is happening here. Don't type >them. >The [?] bits are needed see below. > > As in use the IDE, whatever, to make your changes. >Try them out, fix, etc, etc. This is not really a command line but is >part of what you do "every-day", so to speak. Nor is it anything to do >with git. > ><1> OK, so the fix is looking good. Now we want to get into "git" mode. >(This was the hardest thing I had to come to terms with. git is >actually just a "source code manager" aka "SCM". Some may wish to call >it a "VCS" (Version Control Manager) which it is - if and only if you >are the administrator of the pure source base. If you are as old as I >am perhaps the following may jog some memories "PCVS", "PVCS", etc.) >"git", as in your locally installed "git" only works at the command >line level with the current working directory, i.e. what you get with $ >pwd >So, >[your local repository] is the directory where you cloned the original >gambas source down to. >We are now somewhere where "git" commands can be used. > ><2> This is only "really" necessary if you have added any new files to >your local repository. File deletions and modifications to existing >files are taken care of automagically in the following. You could also >use $ git add [my new file] to tell git about a specific new file, but >"git add *" does take care of any of those little things we may have >forgotten. And by the way it doesn't do any damage. If there are no >new files then it will tell you so. If there are some then it will tell >you that anyway. > >So, where are we at now. In short, "git" now knows that there is new >"stuff" in your local repository. This "stuff" is in the files that >EXIST in your local repository. In other words, if you were to open >one of those files in a text editor, then what you would see is the >file exactly as you left it. BUT we now have to start thinking in "git" >mode. ... > >How can I state this. ... ah, bugger political correctness. >"git" is like your 16 year old son who can't find his football boots on >Saturday morning, but he is "sure" they "should" be exactly where he >left them last Saturday afternoon (i.e. in the middle of the laundry >floor). >So we have to tell him, "No, I cleaned them, polished them and put them >back in your cupboard last Sunday." >Likewise, we have to tell "git" the same type of thing. Hey "git", >your boots are back in the supboard! >This is called a "commit". >So now we know what it is we will > ><3> Then make a commit to your local repository. > -a means that all (sorry, ALL) your local changes will be committed to >your local repository. >-s means that the commit will be signed with your (local or "global" >email name and address) > >So, now the "son", sorry the "git" now knows that you are serious. In >it's tiny little mind it compares it's idea of what the file should >look like to what it actually looks like and comes up with a set of >"differences". Sort of like "son" comparing his mental image of the >laundry floor and the actual contents of the cupboard... thinks "Hmm, >that's strange, the laundry fairies must have moved them?" >Which is why the -s is kind of important. > ><4> > >Woops! I gotta go do stuff. >I'll finish this ;ater. > >b >-- >B Bruen > >------------------------------------------------------------------------------ >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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From taboege at ...176... Mon Aug 21 17:35:03 2017 From: taboege at ...176... (Tobias Boege) Date: Mon, 21 Aug 2017 17:35:03 +0200 Subject: [Gambas-devel] Fwd: Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: <25c6e0fa-4fc4-4a50-9497-721bd6e3c5c9@...176...> References: <20170821155529.13165eb627dd492e50e717f8@...176...> <25c6e0fa-4fc4-4a50-9497-721bd6e3c5c9@...176...> Message-ID: <20170821153503.GI585@...756...> On Mon, 21 Aug 2017, d4t4full at ...176... wrote: > I also wonder why I had to GIT ADD a file that was cloned, tho. Shouldn't Git already know the file WAS modded and that it HAD to be committed? Anyway I didn't commit it signed so I clearly messed up. > That's a feature :-) Imagine you have worked furiously all day and in the evening you realise that you did lots things which you'd rather break up into smaller logical pieces and commit them individually. If you assume that it is desirable to be able to revert commits, then you would want a commit to do just one thing. If you made changes to the IDE and gb.db.odbc in the same commit, simply reverting the commit because you messed up in the IDE would undo your changes to ODBC as well. Someone correcting your mistake would have to separate your changes and just undo the IDE-related part by hand. git lets you go as far as committing only *parts of certain files*, with git add -i. Remember: git is the stupid content tracker. Regards, Tobi -- "There's an old saying: Don't change anything... ever!" -- Mr. Monk From mckaygerhard at ...176... Mon Aug 21 17:52:14 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Mon, 21 Aug 2017 11:52:14 -0400 Subject: [Gambas-devel] Fwd: Cloned and edited. How do I get the changes staged, committed, and then uploaded to GitLab? In-Reply-To: <20170821153503.GI585@...756...> References: <20170821155529.13165eb627dd492e50e717f8@...176...> <25c6e0fa-4fc4-4a50-9497-721bd6e3c5c9@...176...> <20170821153503.GI585@...756...> Message-ID: 2017-08-21 11:35 GMT-04:00 Tobias Boege : > git lets you go as far as committing only *parts of certain files*, with > its true, i forgot that! i can commit partially set of changes in the same archive, and revert part of them > git add -i. Remember: git is the stupid content tracker. > > Regards, > Tobi > > -- > "There's an old saying: Don't change anything... ever!" -- Mr. Monk > > ------------------------------------------------------------ > ------------------ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From d4t4full at ...176... Thu Aug 24 00:49:22 2017 From: d4t4full at ...176... (First Last) Date: Wed, 23 Aug 2017 19:49:22 -0300 Subject: [Gambas-devel] Git merge request for gb.db.odbc. Message-ID: Beno?t, Yesterday I forked gambas' master and edited *main.c* in *gb.db.odbc*:Added and changed several things I was accumulating through time. Made a merge request (still pending, and now 3 commits back) on gambas master for my patch, don't know if I did it right. If not correct, please led me into knowing how to do it right, so I know for next time. Regards, zxMarce. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebikul at ...176... Thu Aug 24 20:46:35 2017 From: sebikul at ...176... (=?UTF-8?Q?Sebasti=C3=A1n_Kulesz?=) Date: Thu, 24 Aug 2017 15:46:35 -0300 Subject: [Gambas-devel] GitLab and PPAs Message-ID: Hi everyone! Sorry for the delay in getting into this, I just got back from an exchange semester. This week I moved the building infrastructure of the PPAs from the SVN repo to the git repo, but I had some problems in the way. First of all, the stable branch in gitlab is not actually the same as the released source archive for Gambas 3.10.0. For everything to work, I would need to have in the stable branch the same code as in the source archive. Right now, I can't speak on the source itself, but the version numbers at least correspond to a developing branch, not to a stable one. I have already pushed builds to the three PPAs, to the stable one without knowing I would have this problem. I don't have access to the gitlab project to change it myself, so please update the version numbers as soon as possible. If there is any difference from the released source archive, that should also be fixed ASAP so that I can issue a new build. Thanks for the help, and sorry again for the delay. Regards, Sebastian -------------- next part -------------- An HTML attachment was scrubbed... URL: From gambas at ...1... Thu Aug 24 21:35:34 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Thu, 24 Aug 2017 21:35:34 +0200 Subject: [Gambas-devel] GitLab and PPAs In-Reply-To: References: Message-ID: Le 24/08/2017 ? 20:46, Sebasti?n Kulesz a ?crit : > Hi everyone! > > Sorry for the delay in getting into this, I just got back from an > exchange semester. > > This week I moved the building infrastructure of the PPAs from the SVN > repo to the git repo, but I had some problems in the way. First of all, > the stable branch in gitlab is not actually the same as the released > source archive for Gambas 3.10.0. > > For everything to work, I would need to have in the stable branch the > same code as in the source archive. Right now, I can't speak on the > source itself, but the version numbers at least correspond to a > developing branch, not to a stable one. "stable" is the equivalent of "/branches/3.10". To get the 3.10.0 code, you must look at the "3.10.0" tag. Anyway I will fix the "stable" version with "3.10.0". Regards, -- Beno?t Minisini From tmorehen at ...755... Fri Aug 25 22:32:17 2017 From: tmorehen at ...755... (Tony Morehen) Date: Fri, 25 Aug 2017 16:32:17 -0400 Subject: [Gambas-devel] BUG: Recent changes to TerminalView stop you from responding to certain prompts Message-ID: When using terminalview in a terminal program, you cannot respond to prompts such as git's requests for username and password. Bash's built-in read command also doesn't work properly.? You can type in text ok, but when you press enter, all you see is "^M" and nothing happens.? All you can do is press control-C to abort. To duplicate: 1) run FTerminalView in gb.form.terminal 2) enter "read -p '>' 3) type some text, press enter 4) all you see is your text + ^M Potential fix: line 673 in TerminalFilter_VT100, change the False action of the IIf from "\r" to "\n" gb.form.terminal must be driving you guys nuts. Cheers, Tony From gambas at ...1... Fri Aug 25 23:10:48 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Fri, 25 Aug 2017 23:10:48 +0200 Subject: [Gambas-devel] BUG: Recent changes to TerminalView stop you from responding to certain prompts In-Reply-To: References: Message-ID: Le 25/08/2017 ? 22:32, Tony Morehen a ?crit : > When using terminalview in a terminal program, you cannot respond to > prompts such as git's requests for username and password. Bash's > built-in read command also doesn't work properly. You can type in text > ok, but when you press enter, all you see is "^M" and nothing happens. > All you can do is press control-C to abort. > > To duplicate: > 1) run FTerminalView in gb.form.terminal > 2) enter "read -p '>' > 3) type some text, press enter > 4) all you see is your text + ^M > > Potential fix: > > line 673 in TerminalFilter_VT100, change the False action of the IIf > from "\r" to "\n" > > gb.form.terminal must be driving you guys nuts. > > Cheers, > Tony > OK, fixed. -- Beno?t Minisini From gbwilly at ...777... Fri Aug 25 23:18:07 2017 From: gbwilly at ...777... (gbwilly at ...777...) Date: Fri, 25 Aug 2017 21:18:07 -0000 Subject: [Gambas-devel] Submitted merge request Message-ID: <20170825211807.BFD984E0024@...778...> Hi all, I submitted a merge request for Dutch translations for gb.term.form. No idea if you get a notification on that at gitLab. So to make sure you know, I post it here. gbWilly From gambas at ...1... Fri Aug 25 23:52:52 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Fri, 25 Aug 2017 23:52:52 +0200 Subject: [Gambas-devel] Submitted merge request In-Reply-To: <20170825211807.BFD984E0024@...778...> References: <20170825211807.BFD984E0024@...778...> Message-ID: Le 25/08/2017 ? 23:18, gbwilly at ...777... a ?crit : > Hi all, > > I submitted a merge request for Dutch translations for gb.term.form. > No idea if you get a notification on that at gitLab. > So to make sure you know, I post it here. > > gbWilly No, but maybe there is a way to get notifications of merge requests and I didn't activate it. Anyway, I regularly go to gitlab, so it's not a big deal. Regards, -- Beno?t Minisini From gambas.fr at ...176... Sat Aug 26 08:37:07 2017 From: gambas.fr at ...176... (Fabien Bodard) Date: Sat, 26 Aug 2017 08:37:07 +0200 Subject: [Gambas-devel] BUG: Recent changes to TerminalView stop you from responding to certain prompts In-Reply-To: References: Message-ID: 2017-08-25 23:10 GMT+02:00 Beno?t Minisini via Gambas-devel : > Le 25/08/2017 ? 22:32, Tony Morehen a ?crit : >> >> When using terminalview in a terminal program, you cannot respond to >> prompts such as git's requests for username and password. Bash's built-in >> read command also doesn't work properly. You can type in text ok, but when >> you press enter, all you see is "^M" and nothing happens. All you can do is >> press control-C to abort. >> >> To duplicate: >> 1) run FTerminalView in gb.form.terminal >> 2) enter "read -p '>' >> 3) type some text, press enter >> 4) all you see is your text + ^M >> >> Potential fix: >> >> line 673 in TerminalFilter_VT100, change the False action of the IIf from >> "\r" to "\n" >> >> gb.form.terminal must be driving you guys nuts. Yes but it's so interresting ! And available emulator are not so numerous too. >> >> Cheers, >> Tony >> > > OK, fixed. > > -- > Beno?t Minisini > > > ------------------------------------------------------------------------------ > 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 -- Fabien Bodard From tmorehen at ...755... Sat Aug 26 14:51:44 2017 From: tmorehen at ...755... (Tony Morehen) Date: Sat, 26 Aug 2017 08:51:44 -0400 Subject: [Gambas-devel] BUG: Recent changes to TerminalView stop you from responding to certain prompts In-Reply-To: References: Message-ID: <740e230b-2929-c2bb-63e0-ce6de7f7f2de@...755...> I know.? One of the first programs I wrote back in the early 80s was a terminal program to let my first IBM-compatible, a 12 mHz 80286, talk to my other computer, a Z80 CP/M machine. Don't get me started on wiring a serial cable.? Back then, nothing was plug'n'play.? Everything, including serial ports, was custom. On 2017-08-26 02:37 AM, Fabien Bodard wrote: > 2017-08-25 23:10 GMT+02:00 Beno?t Minisini via Gambas-devel > : >> Le 25/08/2017 ? 22:32, Tony Morehen a ?crit : >>> When using terminalview in a terminal program, you cannot respond to >>> prompts such as git's requests for username and password. Bash's built-in >>> read command also doesn't work properly. You can type in text ok, but when >>> you press enter, all you see is "^M" and nothing happens. All you can do is >>> press control-C to abort. >>> >>> To duplicate: >>> 1) run FTerminalView in gb.form.terminal >>> 2) enter "read -p '>' >>> 3) type some text, press enter >>> 4) all you see is your text + ^M >>> >>> Potential fix: >>> >>> line 673 in TerminalFilter_VT100, change the False action of the IIf from >>> "\r" to "\n" >>> >>> gb.form.terminal must be driving you guys nuts. > Yes but it's so interresting ! And available emulator are not so numerous too. > > >>> Cheers, >>> Tony >>> >> OK, fixed. >> >> -- >> Beno?t Minisini >> >> >> ------------------------------------------------------------------------------ >> 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 > > From gambas.fr at ...176... Sat Aug 26 19:19:59 2017 From: gambas.fr at ...176... (Fabien Bodard) Date: Sat, 26 Aug 2017 19:19:59 +0200 Subject: [Gambas-devel] BUG: Recent changes to TerminalView stop you from responding to certain prompts In-Reply-To: <740e230b-2929-c2bb-63e0-ce6de7f7f2de@...755...> References: <740e230b-2929-c2bb-63e0-ce6de7f7f2de@...755...> Message-ID: 2017-08-26 14:51 GMT+02:00 Tony Morehen : > I know. One of the first programs I wrote back in the early 80s was a > terminal program to let my first IBM-compatible, a 12 mHz 80286, talk to my > other computer, a Z80 CP/M machine. > > Don't get me started on wiring a serial cable. Back then, nothing was > plug'n'play. Everything, including serial ports, was custom. > You have the luck to known these beautifull years :-). In these days i was only a baby and i've known my first computer only at 12 :-/ So it was in 1990... on m$dos 6 and W3.11. just before linux was born :-). The first computer i've used was a 86286 20Mhz. It took 2 sec to excel to show a letter after pressing the keyboard !!!. In fact, i've discovered the terminals on the late but i keep a good feeling about them for true productivity interconnected programs... better for that than actual cloudified web products. > > On 2017-08-26 02:37 AM, Fabien Bodard wrote: >> >> 2017-08-25 23:10 GMT+02:00 Beno?t Minisini via Gambas-devel >> : >>> >>> Le 25/08/2017 ? 22:32, Tony Morehen a ?crit : >>>> >>>> When using terminalview in a terminal program, you cannot respond to >>>> prompts such as git's requests for username and password. Bash's >>>> built-in >>>> read command also doesn't work properly. You can type in text ok, but >>>> when >>>> you press enter, all you see is "^M" and nothing happens. All you can do >>>> is >>>> press control-C to abort. >>>> >>>> To duplicate: >>>> 1) run FTerminalView in gb.form.terminal >>>> 2) enter "read -p '>' >>>> 3) type some text, press enter >>>> 4) all you see is your text + ^M >>>> >>>> Potential fix: >>>> >>>> line 673 in TerminalFilter_VT100, change the False action of the IIf >>>> from >>>> "\r" to "\n" >>>> >>>> gb.form.terminal must be driving you guys nuts. >> >> Yes but it's so interresting ! And available emulator are not so numerous >> too. >> >> >>>> Cheers, >>>> Tony >>>> >>> OK, fixed. >>> >>> -- >>> Beno?t Minisini >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> 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 >> >> >> > > > > ------------------------------------------------------------------------------ > 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 -- Fabien Bodard From chrisml at ...757... Sat Aug 26 19:34:50 2017 From: chrisml at ...757... (Christof Thalhofer) Date: Sat, 26 Aug 2017 19:34:50 +0200 Subject: [Gambas-devel] GitLab and PPAs In-Reply-To: References: Message-ID: Am 24.08.2017 um 21:35 schrieb Beno?t Minisini via Gambas-devel: >> For everything to work, I would need to have in the stable branch the >> same code as in the source archive. Right now, I can't speak on the >> source itself, but the version numbers at least correspond to a >> developing branch, not to a stable one. > > "stable" is the equivalent of "/branches/3.10". To get the 3.10.0 code, > you must look at the "3.10.0" tag. > > Anyway I will fix the "stable" version with "3.10.0". On launchpad now there is a version called 3.10.0 whithout the fixes you made before releasing 3.10.0 You asked for a last test, I reported, you fixed: b2901f7d41e35b "[DEVELOPMENT ENVIRONMENT] * BUG: Editor: Fix identation of code beautifier on lines ending with an operator and on strings spread over multiple lines." I now tested 3.10.0 from launchpad, it scrambles my code over and over ... because this fix is not in it. Maybe the tag v3.10.0 is set to the wrong commit? It should have been set to 8cd2dba1d4f1169676 ... But it is at this commit: bd1b84afcdafd1961d50b0f809c45eecca5b90eb So it lacks the last fixes ... Alles Gute Christof Thalhofer -- Dies ist keine Signatur -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From gbwilly at ...777... Sat Aug 26 20:51:52 2017 From: gbwilly at ...777... (gbwilly at ...777...) Date: Sat, 26 Aug 2017 18:51:52 -0000 Subject: [Gambas-devel] Question on changelog Message-ID: <20170826185152.EBC304E000D@...778...> In gambas3 there is gambas-wiki and gb.wiki. What slots do I use in changelog for gambas-wiki and gb.wiki? gbWilly From gambas at ...1... Sat Aug 26 21:43:19 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 26 Aug 2017 21:43:19 +0200 Subject: [Gambas-devel] GitLab and PPAs In-Reply-To: References: Message-ID: <7334d111-adf5-4301-4178-6f2e5b44a87d@...1...> Le 26/08/2017 ? 19:34, Christof Thalhofer a ?crit : > Am 24.08.2017 um 21:35 schrieb Beno?t Minisini via Gambas-devel: > >>> For everything to work, I would need to have in the stable branch the >>> same code as in the source archive. Right now, I can't speak on the >>> source itself, but the version numbers at least correspond to a >>> developing branch, not to a stable one. >> >> "stable" is the equivalent of "/branches/3.10". To get the 3.10.0 code, >> you must look at the "3.10.0" tag. >> >> Anyway I will fix the "stable" version with "3.10.0". > > On launchpad now there is a version called 3.10.0 whithout the fixes you > made before releasing 3.10.0 > > You asked for a last test, I reported, you fixed: > > b2901f7d41e35b "[DEVELOPMENT ENVIRONMENT] * BUG: Editor: Fix identation > of code beautifier on lines ending with an operator and on strings > spread over multiple lines." > > I now tested 3.10.0 from launchpad, it scrambles my code over and over > ... because this fix is not in it. > > Maybe the tag v3.10.0 is set to the wrong commit? It should have been set to > > 8cd2dba1d4f1169676 ... > > But it is at this commit: > bd1b84afcdafd1961d50b0f809c45eecca5b90eb > > So it lacks the last fixes ... > > > Alles Gute > > Christof Thalhofer > Yep. Apparently the git tag missed the three last commits of the final 3.10.0. I think I have to add them to the stable branch too. -- Beno?t Minisini From gbwilly at ...777... Sat Aug 26 22:11:38 2017 From: gbwilly at ...777... (gbwilly at ...777...) Date: Sat, 26 Aug 2017 20:11:38 -0000 Subject: [Gambas-devel] Request for merge submitted Message-ID: <20170826201138.E6A964E0008@...778...> Merge request for Dutch translations. All parts and components should e translated to Dutch now. gbWilly From chrisml at ...757... Sat Aug 26 22:58:29 2017 From: chrisml at ...757... (Christof Thalhofer) Date: Sat, 26 Aug 2017 22:58:29 +0200 Subject: [Gambas-devel] GitLab and PPAs In-Reply-To: <7334d111-adf5-4301-4178-6f2e5b44a87d@...1...> References: <7334d111-adf5-4301-4178-6f2e5b44a87d@...1...> Message-ID: Am 26.08.2017 um 21:43 schrieb Beno?t Minisini: > Yep. Apparently the git tag missed the three last commits of the > final 3.10.0. I think I have to add them to the stable branch too. There is no stable branch, just a tag called v3.10.0. I think it makes sense to create a branch called v3.10.1 and cherry-pick the fixes into it. So: git branch v.3.10.1 git checkout v.3.10.1 git cherry-pick 954f3ff7069e55 git cherry-pick b2901f7d41e35b git cherry-pick 8cd2dba1d4f116 Then the branch has to be pushed upstream git push -u origin v3.10.1 AFAIK Alles Gute Christof Thalhofer -- Dies ist keine Signatur -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From gambas at ...1... Sat Aug 26 23:21:17 2017 From: gambas at ...1... (=?UTF-8?Q?Beno=c3=aet_Minisini?=) Date: Sat, 26 Aug 2017 23:21:17 +0200 Subject: [Gambas-devel] GitLab and PPAs In-Reply-To: References: <7334d111-adf5-4301-4178-6f2e5b44a87d@...1...> Message-ID: <3882f459-504e-8f76-10a7-94505e728153@...1...> Le 26/08/2017 ? 22:58, Christof Thalhofer a ?crit : > Am 26.08.2017 um 21:43 schrieb Beno?t Minisini: > >> Yep. Apparently the git tag missed the three last commits of the >> final 3.10.0. I think I have to add them to the stable branch too. > > There is no stable branch, just a tag called v3.10.0. > > I think it makes sense to create a branch called v3.10.1 and cherry-pick > the fixes into it. > > So: > > git branch v.3.10.1 > git checkout v.3.10.1 > git cherry-pick 954f3ff7069e55 > git cherry-pick b2901f7d41e35b > git cherry-pick 8cd2dba1d4f116 > > Then the branch has to be pushed upstream > > git push -u origin v3.10.1 > > AFAIK > > Alles Gute > > Christof Thalhofer > By the way, I'm currently thinking that the easier and the better may be a 3.11 very fast, as soon as the TerminalView and process management is stabilized (it seems now). Because there are far more than these 3 fixed to merge. Regards, -- Beno?t Minisini From chrisml at ...757... Sun Aug 27 00:01:00 2017 From: chrisml at ...757... (Christof Thalhofer) Date: Sun, 27 Aug 2017 00:01:00 +0200 Subject: [Gambas-devel] GitLab and PPAs In-Reply-To: <3882f459-504e-8f76-10a7-94505e728153@...1...> References: <7334d111-adf5-4301-4178-6f2e5b44a87d@...1...> <3882f459-504e-8f76-10a7-94505e728153@...1...> Message-ID: Am 26.08.2017 um 23:21 schrieb Beno?t Minisini: > By the way, I'm currently thinking that the easier and the better may be > a 3.11 very fast, as soon as the TerminalView and process management is > stabilized (it seems now). Because there are far more than these 3 fixed > to merge. No problem, I would stay at 3.9 till then ... Alles Gute Christof Thalhofer -- Dies ist keine Signatur -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From mckaygerhard at ...176... Sun Aug 27 00:03:23 2017 From: mckaygerhard at ...176... (PICCORO McKAY Lenz) Date: Sat, 26 Aug 2017 18:03:23 -0400 Subject: [Gambas-devel] GitLab and PPAs In-Reply-To: References: <7334d111-adf5-4301-4178-6f2e5b44a87d@...1...> <3882f459-504e-8f76-10a7-94505e728153@...1...> Message-ID: Git uses two main types of tags: lightweight and annotated. Gitlab had predefined lightweithg and github annotated.. how are this doing by administrations? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-08-26 18:01 GMT-04:00 Christof Thalhofer : > Am 26.08.2017 um 23:21 schrieb Beno?t Minisini: > > > By the way, I'm currently thinking that the easier and the better may be > > a 3.11 very fast, as soon as the TerminalView and process management is > > stabilized (it seems now). Because there are far more than these 3 fixed > > to merge. > > No problem, I would stay at 3.9 till then ... > > > Alles Gute > > Christof Thalhofer > > -- > Dies ist keine Signatur > > > ------------------------------------------------------------ > ------------------ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmorehen at ...755... Mon Aug 28 17:50:01 2017 From: tmorehen at ...755... (Tony Morehen) Date: Mon, 28 Aug 2017 11:50:01 -0400 Subject: [Gambas-devel] BUG: Recent changes to TerminalView stop you from responding to certain prompts In-Reply-To: References: Message-ID: <985c0470-97b7-b13a-6202-994f18daf302@...755...> Mea Culpa. We need to revert this change. While the fix I proposed did fix read and git's username/password prompts, it broke several terminal-based text editors: nano, joe and micro were the one's I tested.? For the editors, you now need to press ctrl-M to get a new line.? Emacs though works fine. As far as read and git are concerned, you can press ctrl-J to get a new line.? As well "read -e" will accept ctrl-M as new line. Obviously, there is no simple fix.? TerminalView needs to detect whether the application is expecting keyboard input and so will work only with ctrl-M or file-type input (ctrl-J).? I'll follow up on this. Sorry for the mess. Tony On 2017-08-25 05:10 PM, Beno?t Minisini wrote: > Le 25/08/2017 ? 22:32, Tony Morehen a ?crit : >> When using terminalview in a terminal program, you cannot respond to >> prompts such as git's requests for username and password. Bash's >> built-in read command also doesn't work properly.? You can type in >> text ok, but when you press enter, all you see is "^M" and nothing >> happens. All you can do is press control-C to abort. >> >> To duplicate: >> 1) run FTerminalView in gb.form.terminal >> 2) enter "read -p '>' >> 3) type some text, press enter >> 4) all you see is your text + ^M >> >> Potential fix: >> >> line 673 in TerminalFilter_VT100, change the False action of the IIf >> from "\r" to "\n" >> >> gb.form.terminal must be driving you guys nuts. >> >> Cheers, >> Tony >> > > OK, fixed. > From tmorehen at ...755... Tue Aug 29 06:48:28 2017 From: tmorehen at ...755... (Tony Morehen) Date: Tue, 29 Aug 2017 00:48:28 -0400 Subject: [Gambas-devel] BUG: Recent changes to TerminalView stop you from responding to certain prompts In-Reply-To: <985c0470-97b7-b13a-6202-994f18daf302@...755...> References: <985c0470-97b7-b13a-6202-994f18daf302@...755...> Message-ID: <7b72e481-498b-c27f-d345-c89ab00f489b@...755...> I did some more research into this issue and it seems related to what mode the tty is in. There is canonical mode, which is the standard mode using readline ie with line editing and, it seems, CR to NL translation. The other mode is raw mode, where keyboard input is sent directly to the application. The read command uses raw mode. So I tried experimenting with stty. stty raw gave me the step effect on output but the enter keypress appeared to behave normally ie. stty -raw fixed the step effect but then I found that enter now worked in the full screen cli text editors, read, and password prompts! A work-around for this issue. It turns out that stty raw is not symmetric. Further experimenting showed that sending stty icrnl to the terminal on initialization fixes the enter bug. This suggests that adding a property such as EnableCRtoNL to Process.term could be a good approach for a long-term fix. EnableCRtoNL would toggle a flag in the termios structure related to Process.term. On 2017-08-28 11:50 AM, Tony Morehen wrote: > Mea Culpa. > > We need to revert this change. > > While the fix I proposed did fix read and git's username/password > prompts, it broke several terminal-based text editors: nano, joe and > micro were the one's I tested. For the editors, you now need to press > ctrl-M to get a new line. Emacs though works fine. > > As far as read and git are concerned, you can press ctrl-J to get a > new line. As well "read -e" will accept ctrl-M as new line. > > Obviously, there is no simple fix. TerminalView needs to detect > whether the application is expecting keyboard input and so will work > only with ctrl-M or file-type input (ctrl-J). I'll follow up on this. > > Sorry for the mess. > Tony > > > On 2017-08-25 05:10 PM, Beno?t Minisini wrote: >> Le 25/08/2017 ? 22:32, Tony Morehen a ?crit : >>> When using terminalview in a terminal program, you cannot respond to >>> prompts such as git's requests for username and password. Bash's >>> built-in read command also doesn't work properly. You can type in >>> text ok, but when you press enter, all you see is "^M" and nothing >>> happens. All you can do is press control-C to abort. >>> >>> To duplicate: >>> 1) run FTerminalView in gb.form.terminal >>> 2) enter "read -p '>' >>> 3) type some text, press enter >>> 4) all you see is your text + ^M >>> >>> Potential fix: >>> >>> line 673 in TerminalFilter_VT100, change the False action of the IIf >>> from "\r" to "\n" >>> >>> gb.form.terminal must be driving you guys nuts. >>> >>> Cheers, >>> Tony >>> >> >> OK, fixed. >> > > > > ------------------------------------------------------------------------------ > > 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 From tmorehen at ...755... Tue Aug 29 15:13:17 2017 From: tmorehen at ...755... (Tony Morehen) Date: Tue, 29 Aug 2017 09:13:17 -0400 Subject: [Gambas-devel] BUG: Recent changes to TerminalView stop you from responding to certain prompts In-Reply-To: <7b72e481-498b-c27f-d345-c89ab00f489b@...755...> References: <985c0470-97b7-b13a-6202-994f18daf302@...755...> <7b72e481-498b-c27f-d345-c89ab00f489b@...755...> Message-ID: <23a07ad6-1317-bc69-25ce-cd0fc2175a04@...755...> Another approach would be to use termios to detect whether the terminal is in raw or canonical mode and then translate CR to LF appropriately. On 2017-08-29 12:48 AM, Tony Morehen wrote: > I did some more research into this issue and it seems related to what > mode the tty is in.? There is canonical mode, which is the standard > mode using readline ie with line editing and, it seems, CR to NL > translation.? The other mode is raw mode, where keyboard input is sent > directly to the application.? The read command uses raw mode. > > So I tried experimenting with stty.? stty raw gave me the step effect > on output but the enter keypress appeared to behave normally ie.? stty > -raw fixed the step effect but then I found that enter now worked in > the full screen cli text editors, read, and password prompts!? A > work-around for this issue. > > It turns out that stty raw is not symmetric.? Further experimenting > showed that sending stty icrnl to the terminal on initialization fixes > the enter bug. > > This suggests that adding a property such as EnableCRtoNL to > Process.term could be a good approach for a long-term fix. > EnableCRtoNL would toggle a flag in the termios structure related to > Process.term. > > > On 2017-08-28 11:50 AM, Tony Morehen wrote: >> Mea Culpa. >> >> We need to revert this change. >> >> While the fix I proposed did fix read and git's username/password >> prompts, it broke several terminal-based text editors: nano, joe and >> micro were the one's I tested.? For the editors, you now need to >> press ctrl-M to get a new line.? Emacs though works fine. >> >> As far as read and git are concerned, you can press ctrl-J to get a >> new line.? As well "read -e" will accept ctrl-M as new line. >> >> Obviously, there is no simple fix.? TerminalView needs to detect >> whether the application is expecting keyboard input and so will work >> only with ctrl-M or file-type input (ctrl-J).? I'll follow up on this. >> >> Sorry for the mess. >> Tony >> >> >> On 2017-08-25 05:10 PM, Beno?t Minisini wrote: >>> Le 25/08/2017 ? 22:32, Tony Morehen a ?crit : >>>> When using terminalview in a terminal program, you cannot respond >>>> to prompts such as git's requests for username and password. Bash's >>>> built-in read command also doesn't work properly.? You can type in >>>> text ok, but when you press enter, all you see is "^M" and nothing >>>> happens. All you can do is press control-C to abort. >>>> >>>> To duplicate: >>>> 1) run FTerminalView in gb.form.terminal >>>> 2) enter "read -p '>' >>>> 3) type some text, press enter >>>> 4) all you see is your text + ^M >>>> >>>> Potential fix: >>>> >>>> line 673 in TerminalFilter_VT100, change the False action of the >>>> IIf from "\r" to "\n" >>>> >>>> gb.form.terminal must be driving you guys nuts. >>>> >>>> Cheers, >>>> Tony >>>> >>> >>> OK, fixed. >>> >> >> >> >> ------------------------------------------------------------------------------ >> >> 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 > > > > ------------------------------------------------------------------------------ > > 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