Thx for the quick answers.

Concerning the as the default file to download:
1. Is there a way to force a particular file?

Concerning the tags:
1. It would be a great improvement to append the readme with the tags
naming convention.
2. To me a commit named V1.2a is miss-leading as being alpha regardless the
real alpha commit is named V1.2-alpha. Same thing for V1.2b. If you want to
say it is a stable release why not use the term stable. My two cents.
3. In any case, IMO, the default commit shown upfront on sourceforge source
should be the latest stable. People coming just want a straight working
copy. Advanced dev will pick a more specific tag.

Concerning responsiveness:
1. I don't see what kind of report I should do. The overall experience
varies, a lot, often and this is not normal. There is, IMO, nothing else to
say. Personally I don't really care because I am sold to gnoga already...
but its hard to explain/convincing to new users.

I will make a pull request with amendments to the build instructions as I
found them rather imprecise this week-end trying to build on Windows.

@David: I don't know to which host you plan to move but let me recommend
these guys: based in France (Paris), powerful dedicated servers, really
cheap, and the latency is excellent. I'm in Montreal, Canada and got a
steady 80ms ping to my server for the last year:

On Tue, Sep 20, 2016 at 2:28 PM, Pascal <> wrote:

> Hello,
> > Le 20 sept. 2016 à 19:09, David Botton <> a écrit :
> >
> > 1. Not sure
> Seems that the default download file is the last mainly downloaded as
> has 2 and the others only 1.
> >
> > 2. Pascal, do you see any reason we need to have Zanyblue incorporated
> in any regular build unless doing the demos that require it (which perhaps
> should be optional)?
> In deed no, I've already separated it as other dependences in dev_1.3 new
> branch.
> But it was not available on SF until I've just forced a repository refresh!
> Please Olivier checkout commit with release tags (without alpha or beta)
> for stable use of Gnoga like last V1.2a.
> Report to the list or open a ticket if any issues.
> If you want new makefile structure, test V1.3-alpha last commit, use it
> only for testing new features ;-)
> >
> > 3. Comcast, the internet provider where my VM is with Gnoga, for the
> last 2 months has been constantly having issues. I'm looking into other
> providers for the location where I have Gnoga hosted.
> Please Olivier, sending full report is actually helping to improve.
> Your last report from end of July was rather ok.
> >
> >
> >
> > On Tue, Sep 20, 2016 at 12:42 PM Olivier Henley <
>> wrote:
> > 1. On sourceforge the default file to download is! Why?
> > 2. This weekend I had problem building latest from master because of
> Zanyblue. I just gave up.
> > 3. Links at (tools, services, marketplace etc) are not
> working ... or incredibly slow. I managed to open only
> but it took like 30 seconds. I dont want to
> sound bad but rarely worked great. I dont know the server
> limitations but it looks it has some. May I suggest to serve it from
> for 5$ per month (
> >
> > Otherwise, can I help?
> Same as David said, you're welcome.
> >
> HTH, Pascal.
Gnoga-list mailing list

Reply via email to