Discussion:
Pre-release of Gambas 3.5.1
(too old to reply)
Benoît Minisini
2013-11-09 01:19:49 UTC
Permalink
Hi,

Here you can download a non-official pre-release of Gambas 3.5.1:

http://sourceforge.net/projects/gambas/files/gambas3/gambas3-3.5.1.tar.bz2/download

This releases mainly tries to fix the packager, but there are some bug
fixes and new features related to the bug fixes too.

Here is a summary of the changes in the packager:

- The packager now uses the current Gambas major & minor version as
minimum version for component dependencies.

- If a project uses gb.gui, then the packager will create two extra
meta-packages: one for Qt4 support, the other for GTK+ support.

The Qt4 meta-package depends on the application package and the gb.qt4
binary package. The GTK+ meta-package depends on the application package
and the gb.gtk binary package.

If OpenGL is used, the corresponding GUI opengl support packages
(gb.qt4.opengl and gb.gtk.opengl) are added to the dependencies.

- The Ubuntu package naming convention is respected: i.e. there is the
"ubuntu" string in the package name.

- The 'gb.desktop.gnome' component is now visible and explicitely
checkable, so that it becomes an explicit dependency when creating a
binary package with the packager.

- You can specify the package version number: this must be used when you
make and deliver several different packages of the same software release.

Here are the new features:

- Enum.Stopped is a new property that returns if the current enumeration
has been stopped.

- OPEN STRING is a new instruction that allows to use a string as a
stream. Writing to it appends the written data to the end of the string
at the moment.

- Closing a string stream returns the data written to the stream as a
new string.

- WRITE behaves the same way as READ on a memory stream, when dealing
with a string: it writes a null-terminated "C" string.

- OPEN MEMORY and OPEN PIPE are synonymous of the MEMORY and PIPE
instructions alone.

- FileChooser now has support for uncompressing 'zip' files, provided
that the 'zip' utility is installed on the system.

- If 'gb.gui' cannot load a GUI component, it tries the other one. If
nothing works, it aborts.

- The default SDL font file is renamed as "_default.ttf" to prevent
packaging conflicts.

- JSON.Decode() now takes an extra optional argument indicating that
keys having a null value are taken into account inside objects.

- JSONCollection is a new class that represents a JSON object whose some
keys are associated with a 'null' value.

Please test it and report! Let's make 3.5.1 a quiet release. :-)

Regards,
--
Benoît Minisini
Benoît Minisini
2013-11-09 01:24:59 UTC
Permalink
Post by Benoît Minisini
Hi,
http://sourceforge.net/projects/gambas/files/gambas3/gambas3-3.5.1.tar.bz2/download
This releases mainly tries to fix the packager, but there are some bug
fixes and new features related to the bug fixes too.
- The packager now uses the current Gambas major & minor version as
minimum version for component dependencies.
- If a project uses gb.gui, then the packager will create two extra
meta-packages: one for Qt4 support, the other for GTK+ support.
The Qt4 meta-package depends on the application package and the gb.qt4
binary package. The GTK+ meta-package depends on the application package
and the gb.gtk binary package.
If OpenGL is used, the corresponding GUI opengl support packages
(gb.qt4.opengl and gb.gtk.opengl) are added to the dependencies.
- The Ubuntu package naming convention is respected: i.e. there is the
"ubuntu" string in the package name.
- The 'gb.desktop.gnome' component is now visible and explicitely
checkable, so that it becomes an explicit dependency when creating a
binary package with the packager.
- You can specify the package version number: this must be used when you
make and deliver several different packages of the same software release.
- Enum.Stopped is a new property that returns if the current enumeration
has been stopped.
- OPEN STRING is a new instruction that allows to use a string as a
stream. Writing to it appends the written data to the end of the string
at the moment.
- Closing a string stream returns the data written to the stream as a
new string.
- WRITE behaves the same way as READ on a memory stream, when dealing
with a string: it writes a null-terminated "C" string.
- OPEN MEMORY and OPEN PIPE are synonymous of the MEMORY and PIPE
instructions alone.
- FileChooser now has support for uncompressing 'zip' files, provided
that the 'zip' utility is installed on the system.
- If 'gb.gui' cannot load a GUI component, it tries the other one. If
nothing works, it aborts.
- The default SDL font file is renamed as "_default.ttf" to prevent
packaging conflicts.
- JSON.Decode() now takes an extra optional argument indicating that
keys having a null value are taken into account inside objects.
- JSONCollection is a new class that represents a JSON object whose some
keys are associated with a 'null' value.
Please test it and report! Let's make 3.5.1 a quiet release. :-)
Regards,
The full ChangeLog is in the wiki:

http://gambasdoc.org/help/doc/release/3.5.1?v3
--
Benoît Minisini
Kende Krisztián
2013-11-09 11:02:52 UTC
Permalink
Post by Benoît Minisini
Hi,
http://sourceforge.net/projects/gambas/files/gambas3/gambas3-3.5.1.tar.bz2/download
This releases mainly tries to fix the packager, but there are some bug
fixes and new features related to the bug fixes too.
- The packager now uses the current Gambas major & minor version as
minimum version for component dependencies.
- If a project uses gb.gui, then the packager will create two extra
meta-packages: one for Qt4 support, the other for GTK+ support.
The Qt4 meta-package depends on the application package and the gb.qt4
binary package. The GTK+ meta-package depends on the application package
and the gb.gtk binary package.
If OpenGL is used, the corresponding GUI opengl support packages
(gb.qt4.opengl and gb.gtk.opengl) are added to the dependencies.
- The Ubuntu package naming convention is respected: i.e. there is the
"ubuntu" string in the package name.
- The 'gb.desktop.gnome' component is now visible and explicitely
checkable, so that it becomes an explicit dependency when creating a
binary package with the packager.
- You can specify the package version number: this must be used when you
make and deliver several different packages of the same software release.
- Enum.Stopped is a new property that returns if the current enumeration
has been stopped.
- OPEN STRING is a new instruction that allows to use a string as a
stream. Writing to it appends the written data to the end of the string
at the moment.
- Closing a string stream returns the data written to the stream as a
new string.
- WRITE behaves the same way as READ on a memory stream, when dealing
with a string: it writes a null-terminated "C" string.
- OPEN MEMORY and OPEN PIPE are synonymous of the MEMORY and PIPE
instructions alone.
- FileChooser now has support for uncompressing 'zip' files, provided
that the 'zip' utility is installed on the system.
- If 'gb.gui' cannot load a GUI component, it tries the other one. If
nothing works, it aborts.
- The default SDL font file is renamed as "_default.ttf" to prevent
packaging conflicts.
- JSON.Decode() now takes an extra optional argument indicating that
keys having a null value are taken into account inside objects.
- JSONCollection is a new class that represents a JSON object whose some
keys are associated with a 'null' value.
Please test it and report! Let's make 3.5.1 a quiet release. :-)
Regards,
Hm, new features... So, it's not backward compatible with 3.5.0 runtime?
Benoît Minisini
2013-11-09 17:52:32 UTC
Permalink
Post by Kende Krisztián
Post by Benoît Minisini
Hi,
http://sourceforge.net/projects/gambas/files/gambas3/gambas3-3.5.1.tar.bz2/download
This releases mainly tries to fix the packager, but there are some bug
fixes and new features related to the bug fixes too.
- The packager now uses the current Gambas major & minor version as
minimum version for component dependencies.
- If a project uses gb.gui, then the packager will create two extra
meta-packages: one for Qt4 support, the other for GTK+ support.
The Qt4 meta-package depends on the application package and the gb.qt4
binary package. The GTK+ meta-package depends on the application package
and the gb.gtk binary package.
If OpenGL is used, the corresponding GUI opengl support packages
(gb.qt4.opengl and gb.gtk.opengl) are added to the dependencies.
- The Ubuntu package naming convention is respected: i.e. there is the
"ubuntu" string in the package name.
- The 'gb.desktop.gnome' component is now visible and explicitely
checkable, so that it becomes an explicit dependency when creating a
binary package with the packager.
- You can specify the package version number: this must be used when you
make and deliver several different packages of the same software release.
- Enum.Stopped is a new property that returns if the current enumeration
has been stopped.
- OPEN STRING is a new instruction that allows to use a string as a
stream. Writing to it appends the written data to the end of the string
at the moment.
- Closing a string stream returns the data written to the stream as a
new string.
- WRITE behaves the same way as READ on a memory stream, when dealing
with a string: it writes a null-terminated "C" string.
- OPEN MEMORY and OPEN PIPE are synonymous of the MEMORY and PIPE
instructions alone.
- FileChooser now has support for uncompressing 'zip' files, provided
that the 'zip' utility is installed on the system.
- If 'gb.gui' cannot load a GUI component, it tries the other one. If
nothing works, it aborts.
- The default SDL font file is renamed as "_default.ttf" to prevent
packaging conflicts.
- JSON.Decode() now takes an extra optional argument indicating that
keys having a null value are taken into account inside objects.
- JSONCollection is a new class that represents a JSON object whose some
keys are associated with a 'null' value.
Please test it and report! Let's make 3.5.1 a quiet release. :-)
Regards,
Hm, new features... So, it's not backward compatible with 3.5.0 runtime?
Yes. But that's not a big deal:

- Gambas 3.5.0 should not be used because of packager issues.

- OPEN STRING and the memory stream changes are actually language fixes.

- Enum.Stopped was needed to fix the JSON.Decode() method.
--
Benoît Minisini
Kende Krisztián
2013-11-09 18:06:40 UTC
Permalink
Post by Benoît Minisini
Post by Kende Krisztián
Post by Benoît Minisini
Hi,
http://sourceforge.net/projects/gambas/files/gambas3/gambas3-3.5.1.tar.bz2/download
This releases mainly tries to fix the packager, but there are some bug
fixes and new features related to the bug fixes too.
- The packager now uses the current Gambas major & minor version as
minimum version for component dependencies.
- If a project uses gb.gui, then the packager will create two extra
meta-packages: one for Qt4 support, the other for GTK+ support.
The Qt4 meta-package depends on the application package and the gb.qt4
binary package. The GTK+ meta-package depends on the application package
and the gb.gtk binary package.
If OpenGL is used, the corresponding GUI opengl support packages
(gb.qt4.opengl and gb.gtk.opengl) are added to the dependencies.
- The Ubuntu package naming convention is respected: i.e. there is the
"ubuntu" string in the package name.
- The 'gb.desktop.gnome' component is now visible and explicitely
checkable, so that it becomes an explicit dependency when creating a
binary package with the packager.
- You can specify the package version number: this must be used when you
make and deliver several different packages of the same software release.
- Enum.Stopped is a new property that returns if the current enumeration
has been stopped.
- OPEN STRING is a new instruction that allows to use a string as a
stream. Writing to it appends the written data to the end of the string
at the moment.
- Closing a string stream returns the data written to the stream as a
new string.
- WRITE behaves the same way as READ on a memory stream, when dealing
with a string: it writes a null-terminated "C" string.
- OPEN MEMORY and OPEN PIPE are synonymous of the MEMORY and PIPE
instructions alone.
- FileChooser now has support for uncompressing 'zip' files, provided
that the 'zip' utility is installed on the system.
- If 'gb.gui' cannot load a GUI component, it tries the other one. If
nothing works, it aborts.
- The default SDL font file is renamed as "_default.ttf" to prevent
packaging conflicts.
- JSON.Decode() now takes an extra optional argument indicating that
keys having a null value are taken into account inside objects.
- JSONCollection is a new class that represents a JSON object whose some
keys are associated with a 'null' value.
Please test it and report! Let's make 3.5.1 a quiet release. :-)
Regards,
Hm, new features... So, it's not backward compatible with 3.5.0 runtime?
- Gambas 3.5.0 should not be used because of packager issues.
- OPEN STRING and the memory stream changes are actually language fixes.
- Enum.Stopped was needed to fix the JSON.Decode() method.
OK, I see.
I uploaded this pre-release to nemh/gambas3 PPA, and some users already
use updated packages. Wait for the bug reports. :-)
Kende Krisztián
2013-11-13 17:16:45 UTC
Permalink
It seems that this was a very well done release. Gambas3-runtime was
downloaded ~15.000 times from nemh/gambas3 PPA, so far, no bug reports. :-)

Kendek
Benoît Minisini
2013-11-13 17:46:08 UTC
Permalink
Post by Kende Krisztián
It seems that this was a very well done release. Gambas3-runtime was
downloaded ~15.000 times from nemh/gambas3 PPA, so far, no bug reports. :-)
Kendek
15000 times! OK, I will make it official..
--
Benoît Minisini
Willy Raets
2013-11-14 14:11:32 UTC
Permalink
Post by Kende Krisztián
It seems that this was a very well done release. Gambas3-runtime was
downloaded ~15.000 times from nemh/gambas3 PPA, so far, no bug reports. :-)
Here is what happens on my test system.
It is a replication of Gambas applications running in a production
environment, installed using .deb packages.

I'll first give you some details on the situation.

The system had Gambas 3.4.2 applications installed (no Gambas IDE as it
is on end user sytems).
The Gambas applications installed:
App 1
-> depends on gb.args, gb.desktop, gb.form, gb.gui, gb.image,
gb.net.curl, gb.net.smtp, gb.settings
-> depends on a Gambas library depending on gb.gui, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.settings

Apps 2 and 3
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings

Apps 4
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.qt4.webkit, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings

App 5
-> depends on gb.args, gb.form, gb.image, gb.mime, gb.qt4, gb.settings

When updating from 3.4.2 to 3.5.1 these parts get updated:
gambas3-gb-cairo
gambas3-gb-form
gambas3-gb-gtk
gambas3-gb-image
gambas3-gb-net
gambas3-gb-net-curl
gambas3-gb-qt4
gambas3-gb-qt4-ext
gambas3-gb-qt4-webkit

All other parts stayed at 3.4.2 and where not updated.
After this none of the applications would install!!

So I upgraded gambas3-runtime (still at 3.4.2) to 3.5.1
This caused App 1 + Gambas library it needs to be removed
This caused App 5 to be uninstalled

App 2, 3 and 4 still run, although following components are still on
3.4.2 version:
gambas3-gb-args
gambas3-gb-desktop
gambas3-gb-net-smtp

I did upgrade them to 3.5.1 after testing the Apps.

The Gambas library using gb.gui can not be reinstalled
Dependency error = gambas3-gb-gui (>=3.0.90).
Because of this App 1 can't be installed as it depends on above Gambas
library.

App 5 did reinstall and I still wonder why it got removed!!
Could be an older version of the app using gb.gtk was still installed.
The newest version used gb.qt4, at that seems to be okay.

It seems that gb.gui apps will not install if there are other Gambas
apps installed using gb.qt4.

The system is a Lubuntu 12.04 LXDE, so gb.gui would prefer using gb.gtk.
What has changed that Gambas apps using gb.gtk and gb.qt4 can't run on
the same system?

So seems I'll need to stick to 3.4.2 a bit longer in a production
environment.

@ Benoît:
Fact that gb.media will not run an a Ubuntu 12.04 is another of my
concerns. In production and personal environment I always stick to the
latest stable release (being 12.04 in buntu with a 5 year support cycle)
and this advise I also give to friends that I got onto linux.

Why does Gambas need to depend on stuff that doesn't run on the latest
stable releases that are just 1 1/2 year out there and will be used for
several years to come.
Do we really need these hight dependencies when they only run on the
latest unstable releases (releases I only run the in VMs for testing
purposes and would never consider using in a production environment).

I aim at running systems unchanged as long as possible, meaning a much
lower cost of ownership. So if Ubuntu 12.05 comes with a 5 year service,
it will run for at least 5 years in the production environment it is
being used. Why change what works just fine? Just because there is some
new fancy stuff out there?

I am migrating a Windows production environment to Linux and all custom
written apps from VB to Gambas. The apps are used 7 days a week, 365
days a year for 13 hours a day. For the migration to work I can't afford
future components not being able to install because the OS running at
work are 2 years old.

I really need some clarity here, before continuing with the migration to
Gambas as I don't want an upgrade to a higher version of Gambas break
stuff that worked just fine, purely because of dependencies that can't
be met.
--
Kind regards,

Willy (aka gbWilly)

http://gambasshowcase.org/
http://howtogambas.org
http://gambos.org
Kende Krisztián
2013-11-15 11:15:22 UTC
Permalink
Post by Willy Raets
Post by Kende Krisztián
It seems that this was a very well done release. Gambas3-runtime was
downloaded ~15.000 times from nemh/gambas3 PPA, so far, no bug reports. :-)
Here is what happens on my test system.
It is a replication of Gambas applications running in a production
environment, installed using .deb packages.
I'll first give you some details on the situation.
The system had Gambas 3.4.2 applications installed (no Gambas IDE as it
is on end user sytems).
App 1
-> depends on gb.args, gb.desktop, gb.form, gb.gui, gb.image,
gb.net.curl, gb.net.smtp, gb.settings
-> depends on a Gambas library depending on gb.gui, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.settings
Apps 2 and 3
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings
Apps 4
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.qt4.webkit, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings
App 5
-> depends on gb.args, gb.form, gb.image, gb.mime, gb.qt4, gb.settings
gambas3-gb-cairo
gambas3-gb-form
gambas3-gb-gtk
gambas3-gb-image
gambas3-gb-net
gambas3-gb-net-curl
gambas3-gb-qt4
gambas3-gb-qt4-ext
gambas3-gb-qt4-webkit
All other parts stayed at 3.4.2 and where not updated.
After this none of the applications would install!!
So I upgraded gambas3-runtime (still at 3.4.2) to 3.5.1
This caused App 1 + Gambas library it needs to be removed
This caused App 5 to be uninstalled
App 2, 3 and 4 still run, although following components are still on
gambas3-gb-args
gambas3-gb-desktop
gambas3-gb-net-smtp
I did upgrade them to 3.5.1 after testing the Apps.
The Gambas library using gb.gui can not be reinstalled
Dependency error = gambas3-gb-gui (>=3.0.90).
Because of this App 1 can't be installed as it depends on above Gambas
library.
App 5 did reinstall and I still wonder why it got removed!!
Could be an older version of the app using gb.gtk was still installed.
The newest version used gb.qt4, at that seems to be okay.
It seems that gb.gui apps will not install if there are other Gambas
apps installed using gb.qt4.
The system is a Lubuntu 12.04 LXDE, so gb.gui would prefer using gb.gtk.
What has changed that Gambas apps using gb.gtk and gb.qt4 can't run on
the same system?
So seems I'll need to stick to 3.4.2 a bit longer in a production
environment.
This is a fixed Gambas bug in the integrated packager. Please re-build
the installation packages with Gambas 3.5.1 IDE.
(I prefer the manual building.)
Post by Willy Raets
Fact that gb.media will not run an a Ubuntu 12.04 is another of my
concerns. In production and personal environment I always stick to the
latest stable release (being 12.04 in buntu with a 5 year support cycle)
and this advise I also give to friends that I got onto linux.
Why does Gambas need to depend on stuff that doesn't run on the latest
stable releases that are just 1 1/2 year out there and will be used for
several years to come.
Do we really need these hight dependencies when they only run on the
latest unstable releases (releases I only run the in VMs for testing
purposes and would never consider using in a production environment).
I aim at running systems unchanged as long as possible, meaning a much
lower cost of ownership. So if Ubuntu 12.05 comes with a 5 year service,
it will run for at least 5 years in the production environment it is
being used. Why change what works just fine? Just because there is some
new fancy stuff out there?
I am migrating a Windows production environment to Linux and all custom
written apps from VB to Gambas. The apps are used 7 days a week, 365
days a year for 13 hours a day. For the migration to work I can't afford
future components not being able to install because the OS running at
work are 2 years old.
I really need some clarity here, before continuing with the migration to
Gambas as I don't want an upgrade to a higher version of Gambas break
stuff that worked just fine, purely because of dependencies that can't
be met.
If you want, I backport the new 'gb.media' component.

Kendek
Willy Raets
2013-11-15 11:58:03 UTC
Permalink
Post by Kende Krisztián
Post by Willy Raets
Post by Kende Krisztián
It seems that this was a very well done release. Gambas3-runtime was
downloaded ~15.000 times from nemh/gambas3 PPA, so far, no bug reports. :-)
Here is what happens on my test system.
It is a replication of Gambas applications running in a production
environment, installed using .deb packages.
I'll first give you some details on the situation.
The system had Gambas 3.4.2 applications installed (no Gambas IDE as it
is on end user sytems).
App 1
-> depends on gb.args, gb.desktop, gb.form, gb.gui, gb.image,
gb.net.curl, gb.net.smtp, gb.settings
-> depends on a Gambas library depending on gb.gui, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.settings
Apps 2 and 3
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings
Apps 4
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.qt4.webkit, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings
App 5
-> depends on gb.args, gb.form, gb.image, gb.mime, gb.qt4, gb.settings
gambas3-gb-cairo
gambas3-gb-form
gambas3-gb-gtk
gambas3-gb-image
gambas3-gb-net
gambas3-gb-net-curl
gambas3-gb-qt4
gambas3-gb-qt4-ext
gambas3-gb-qt4-webkit
All other parts stayed at 3.4.2 and where not updated.
After this none of the applications would install!!
So I upgraded gambas3-runtime (still at 3.4.2) to 3.5.1
This caused App 1 + Gambas library it needs to be removed
This caused App 5 to be uninstalled
App 2, 3 and 4 still run, although following components are still on
gambas3-gb-args
gambas3-gb-desktop
gambas3-gb-net-smtp
I did upgrade them to 3.5.1 after testing the Apps.
The Gambas library using gb.gui can not be reinstalled
Dependency error = gambas3-gb-gui (>=3.0.90).
Because of this App 1 can't be installed as it depends on above Gambas
library.
App 5 did reinstall and I still wonder why it got removed!!
Could be an older version of the app using gb.gtk was still installed.
The newest version used gb.qt4, at that seems to be okay.
It seems that gb.gui apps will not install if there are other Gambas
apps installed using gb.qt4.
The system is a Lubuntu 12.04 LXDE, so gb.gui would prefer using gb.gtk.
What has changed that Gambas apps using gb.gtk and gb.qt4 can't run on
the same system?
So seems I'll need to stick to 3.4.2 a bit longer in a production
environment.
This is a fixed Gambas bug in the integrated packager. Please re-build
the installation packages with Gambas 3.5.1 IDE.
(I prefer the manual building.)
So repackaging the applications in 3.5.1 IDE will solve the problem.
Great, I'll have a go at it, thanks
Post by Kende Krisztián
Post by Willy Raets
Fact that gb.media will not run an a Ubuntu 12.04 is another of my
concerns. In production and personal environment I always stick to the
latest stable release (being 12.04 in buntu with a 5 year support cycle)
and this advise I also give to friends that I got onto linux.
Why does Gambas need to depend on stuff that doesn't run on the latest
stable releases that are just 1 1/2 year out there and will be used for
several years to come.
Do we really need these hight dependencies when they only run on the
latest unstable releases (releases I only run the in VMs for testing
purposes and would never consider using in a production environment).
I aim at running systems unchanged as long as possible, meaning a much
lower cost of ownership. So if Ubuntu 12.05 comes with a 5 year service,
it will run for at least 5 years in the production environment it is
being used. Why change what works just fine? Just because there is some
new fancy stuff out there?
I am migrating a Windows production environment to Linux and all custom
written apps from VB to Gambas. The apps are used 7 days a week, 365
days a year for 13 hours a day. For the migration to work I can't afford
future components not being able to install because the OS running at
work are 2 years old.
I really need some clarity here, before continuing with the migration to
Gambas as I don't want an upgrade to a higher version of Gambas break
stuff that worked just fine, purely because of dependencies that can't
be met.
If you want, I backport the new 'gb.media' component.
Backport, I like that word :)
Would be great, thanks.
--
Kind regards,

Willy (aka gbWilly)

http://gambasshowcase.org/
http://howtogambas.org
http://gambos.org
Kende Krisztián
2013-11-16 13:30:34 UTC
Permalink
Post by Willy Raets
Post by Kende Krisztián
If you want, I backport the new 'gb.media' component.
Backport, I like that word :)
Would be great, thanks.
Now, 'gb.media' and 'gb.jit' (with llvm-3.2) components are successfully
available on Ubuntu Precise. So, all of the components, nothing
disabled. :-)

Kendek
Benoît Minisini
2013-11-15 13:13:44 UTC
Permalink
Post by Willy Raets
Post by Kende Krisztián
It seems that this was a very well done release. Gambas3-runtime was
downloaded ~15.000 times from nemh/gambas3 PPA, so far, no bug reports. :-)
Here is what happens on my test system.
It is a replication of Gambas applications running in a production
environment, installed using .deb packages.
I'll first give you some details on the situation.
The system had Gambas 3.4.2 applications installed (no Gambas IDE as it
is on end user sytems).
App 1
-> depends on gb.args, gb.desktop, gb.form, gb.gui, gb.image,
gb.net.curl, gb.net.smtp, gb.settings
-> depends on a Gambas library depending on gb.gui, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.settings
Apps 2 and 3
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings
Apps 4
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.qt4.webkit, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings
App 5
-> depends on gb.args, gb.form, gb.image, gb.mime, gb.qt4, gb.settings
gambas3-gb-cairo
gambas3-gb-form
gambas3-gb-gtk
gambas3-gb-image
gambas3-gb-net
gambas3-gb-net-curl
gambas3-gb-qt4
gambas3-gb-qt4-ext
gambas3-gb-qt4-webkit
All other parts stayed at 3.4.2 and where not updated.
After this none of the applications would install!!
So I upgraded gambas3-runtime (still at 3.4.2) to 3.5.1
This caused App 1 + Gambas library it needs to be removed
This caused App 5 to be uninstalled
App 2, 3 and 4 still run, although following components are still on
gambas3-gb-args
gambas3-gb-desktop
gambas3-gb-net-smtp
I did upgrade them to 3.5.1 after testing the Apps.
The Gambas library using gb.gui can not be reinstalled
Dependency error = gambas3-gb-gui (>=3.0.90).
Because of this App 1 can't be installed as it depends on above Gambas
library.
App 5 did reinstall and I still wonder why it got removed!!
Could be an older version of the app using gb.gtk was still installed.
The newest version used gb.qt4, at that seems to be okay.
It seems that gb.gui apps will not install if there are other Gambas
apps installed using gb.qt4.
The system is a Lubuntu 12.04 LXDE, so gb.gui would prefer using gb.gtk.
What has changed that Gambas apps using gb.gtk and gb.qt4 can't run on
the same system?
So seems I'll need to stick to 3.4.2 a bit longer in a production
environment.
Fact that gb.media will not run an a Ubuntu 12.04 is another of my
concerns. In production and personal environment I always stick to the
latest stable release (being 12.04 in buntu with a 5 year support cycle)
and this advise I also give to friends that I got onto linux.
Why does Gambas need to depend on stuff that doesn't run on the latest
stable releases that are just 1 1/2 year out there and will be used for
several years to come.
Do we really need these hight dependencies when they only run on the
latest unstable releases (releases I only run the in VMs for testing
purposes and would never consider using in a production environment).
I aim at running systems unchanged as long as possible, meaning a much
lower cost of ownership. So if Ubuntu 12.05 comes with a 5 year service,
it will run for at least 5 years in the production environment it is
being used. Why change what works just fine? Just because there is some
new fancy stuff out there?
I am migrating a Windows production environment to Linux and all custom
written apps from VB to Gambas. The apps are used 7 days a week, 365
days a year for 13 hours a day. For the migration to work I can't afford
future components not being able to install because the OS running at
work are 2 years old.
I really need some clarity here, before continuing with the migration to
Gambas as I don't want an upgrade to a higher version of Gambas break
stuff that worked just fine, purely because of dependencies that can't
be met.
gb.media was done with gstreamer-0.10. But gstreamer-0.10 is not
finished, so to really finish the gb.media component, I had to switch to
gstreamer-1.0.

You should better ask Ubuntu why they don't backport gstreamer-1.0 on
their LTS release instead of keeping a non-finished version of gstreamer.

Note if you use OpenGL (just an example), you will get the same problem,
but at driver's level: they are not finished.

In another words: I won't make Gambas depend on Ubuntu decisions and
organization. And if you want stability, look at the library you are
using to see if they are really finished. If you don't know, ask before.
--
Benoît Minisini
Sebastian Kulesz
2013-11-18 15:10:38 UTC
Permalink
I wanted to step in earlier but with finals coming closer i'm short of time.

I believe you are mixing a few things here. Ubuntu 12.04 is not the latest
stable release, 13.10 is, 12.04 is the latest release with LTS, which is a
completely different thing, and i understand that you want to stick with it
until it reaches EOL, but here is your problem:
There is no LTS or EOL policy with Gambas, there are only stable, daily and
old releases. We don't have the manpower to maintain an LTS release, and
with the packages in the official repositories being old and corrupt,
everyone is forced to use the Stable PPA.

The thing is, keeping a package updated like a rolling release
distribution, under a distro with LTS support will cause you a lot of
trouble with dependencies. You are already experiencing this! There is no
point to backport gstreamer-1.0, because that would mean recompiling every
package that uses it, and thus breaking the stability you are mentioning
that makes an LTS release.

So, if you want to stick with Ubuntu 12.04, don't keep updating Gambas! Use
the same policy Ubuntu uses. Choose a release that works, and stick with
it! If Ubuntu does an Import Freeze, you should too.
If you need the latest features available in Gambas, then you will also
need the latest packages Ubuntu publishes.

Summing up: you either update both, or none.
Choosing one will also cause stability issues: If you install updated
versions of packages already available in the repositories you are
contradicting the reason you want to stick with LTS (which is sticking with
versions known to be stable).

If you really need gb.media to be updated, look for other options. You have
a PPA available here [0] which will install gstreamer-1.0 along with the
default gstreamer-0.10.

Kendek: By backporting gb.media and gb.jit you are restricting me from
asking an Ubuntu MOTU to sync the Gambas packages for older series with
your PPA once the Debian repository is updated. They will not accept a
package which has a dependency not available in the official repos.

[0]
https://launchpad.net/~gstreamer-developers/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=precise
Post by Willy Raets
Post by Kende Krisztián
It seems that this was a very well done release. Gambas3-runtime was
downloaded ~15.000 times from nemh/gambas3 PPA, so far, no bug reports.
:-)
Here is what happens on my test system.
It is a replication of Gambas applications running in a production
environment, installed using .deb packages.
I'll first give you some details on the situation.
The system had Gambas 3.4.2 applications installed (no Gambas IDE as it
is on end user sytems).
App 1
-> depends on gb.args, gb.desktop, gb.form, gb.gui, gb.image,
gb.net.curl, gb.net.smtp, gb.settings
-> depends on a Gambas library depending on gb.gui, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.settings
Apps 2 and 3
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings
Apps 4
-> depends on gb.args, gb.cairo, gb.desktop, gb.form, gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.qt4.ext, gb.qt4.webkit, gb.settings
-> depends on a Gambas library depending on gb.image, gb.net,
gb.net.curl, gb.net.smtp, gb.qt4, gb.settings
App 5
-> depends on gb.args, gb.form, gb.image, gb.mime, gb.qt4, gb.settings
gambas3-gb-cairo
gambas3-gb-form
gambas3-gb-gtk
gambas3-gb-image
gambas3-gb-net
gambas3-gb-net-curl
gambas3-gb-qt4
gambas3-gb-qt4-ext
gambas3-gb-qt4-webkit
All other parts stayed at 3.4.2 and where not updated.
After this none of the applications would install!!
So I upgraded gambas3-runtime (still at 3.4.2) to 3.5.1
This caused App 1 + Gambas library it needs to be removed
This caused App 5 to be uninstalled
App 2, 3 and 4 still run, although following components are still on
gambas3-gb-args
gambas3-gb-desktop
gambas3-gb-net-smtp
I did upgrade them to 3.5.1 after testing the Apps.
The Gambas library using gb.gui can not be reinstalled
Dependency error = gambas3-gb-gui (>=3.0.90).
Because of this App 1 can't be installed as it depends on above Gambas
library.
App 5 did reinstall and I still wonder why it got removed!!
Could be an older version of the app using gb.gtk was still installed.
The newest version used gb.qt4, at that seems to be okay.
It seems that gb.gui apps will not install if there are other Gambas
apps installed using gb.qt4.
The system is a Lubuntu 12.04 LXDE, so gb.gui would prefer using gb.gtk.
What has changed that Gambas apps using gb.gtk and gb.qt4 can't run on
the same system?
So seems I'll need to stick to 3.4.2 a bit longer in a production
environment.
Fact that gb.media will not run an a Ubuntu 12.04 is another of my
concerns. In production and personal environment I always stick to the
latest stable release (being 12.04 in buntu with a 5 year support cycle)
and this advise I also give to friends that I got onto linux.
Why does Gambas need to depend on stuff that doesn't run on the latest
stable releases that are just 1 1/2 year out there and will be used for
several years to come.
Do we really need these hight dependencies when they only run on the
latest unstable releases (releases I only run the in VMs for testing
purposes and would never consider using in a production environment).
I aim at running systems unchanged as long as possible, meaning a much
lower cost of ownership. So if Ubuntu 12.05 comes with a 5 year service,
it will run for at least 5 years in the production environment it is
being used. Why change what works just fine? Just because there is some
new fancy stuff out there?
I am migrating a Windows production environment to Linux and all custom
written apps from VB to Gambas. The apps are used 7 days a week, 365
days a year for 13 hours a day. For the migration to work I can't afford
future components not being able to install because the OS running at
work are 2 years old.
I really need some clarity here, before continuing with the migration to
Gambas as I don't want an upgrade to a higher version of Gambas break
stuff that worked just fine, purely because of dependencies that can't
be met.
--
Kind regards,
Willy (aka gbWilly)
http://gambasshowcase.org/
http://howtogambas.org
http://gambos.org
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Gambas-user mailing list
https://lists.sourceforge.net/lists/listinfo/gambas-user
Kende Krisztián
2013-11-18 15:54:59 UTC
Permalink
Post by Sebastian Kulesz
Kendek: By backporting gb.media and gb.jit you are restricting me from
asking an Ubuntu MOTU to sync the Gambas packages for older series with
your PPA once the Debian repository is updated. They will not accept a
package which has a dependency not available in the official repos.
[0]
https://launchpad.net/~gstreamer-developers/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=precise
It's unlikely. Ubuntu developers are not backporting Gambas packages in
Ubuntu 12.04 official repository. But the llvm-3.2 has been backported
(LP: #1177679), just armhf packages are not available (I created in the
nemh/gambas3 PPA).

In any case, the gstreamer can be ported back, it's completely separate,
like llvm-3.2. Or they simply rewrite the source. The Ubuntu developers
are talented programmers, they clearly understand the Python language
(or not...).

Kendek

PICCORO McKAY Lenz
2013-11-15 13:49:36 UTC
Permalink
Post by Willy Raets
it will run for at least 5 years in the production environment it is
being used. Why change what works just fine? Just because there is some
new fancy stuff out there?
i 'm running a payroll system in debian lenny, 24/7 at 365 days and
ther's no reason to "upgrade" to winbuntu 10000 or debian "unstable"
due are the "lasted"
u have right men! that's stupid! why changes if works perfectly!!!
Post by Willy Raets
Fact that gb.media will not run an a Ubuntu 12.04 is another of my
concerns. In production and personal environment I always stick to the
latest stable release (being 12.04 in buntu with a 5 year support cycle)
and this advise I also give to friends that I got onto linux.
This was cuase ddue benoit use "too moderm up-to-date ultimate release
version" of gstreamer
i'm tyred of the software always constant in "upgrades upgrades upgrades"

of course, developer do not note that:
constant movement for support constant globalization! more upgrades
raises more requerimients so then more power to need so intel and amd
sell more and more
Post by Willy Raets
Why does Gambas need to depend on stuff that doesn't run on the latest
stable releases that are just 1 1/2 year out there and will be used for
several years to come.
Do we really need these hight dependencies when they only run on the
latest unstable releases (releases I only run the in VMs for testing
purposes and would never consider using in a production environment).ç
Another case are that the typically response "upgrade to lasted, its
fixed there"
so then stable releases are not fixed?
Post by Willy Raets
Post by Kende Krisztián
If you want, I backport the new 'gb.media' component.
i try to backport the gb.media component, but do not work, i
backported for squeeze, for wheeze and for lenny inclusivelly the
gstreamer 0.10.31 (all componentes, and packages) and compile with
lasted ffmpeg, codecs etc, all repository have amount (including
packages for that taks) 8Gb..

but gb.media do not compile and said requeriments for 3.4.X only need
gstreamer 0.10.30 as minimun, i have instaled, correctly packages and
backported base sgtremaer 0.10.31, and 0.10.19 bad plugins, etc etc
and do not enable the compilation

nobody care this due are focused in "lasted up to date moderm stuff"
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Kende Krisztián
2013-11-15 14:00:37 UTC
Permalink
Post by PICCORO McKAY Lenz
Post by Kende Krisztián
If you want, I backport the new 'gb.media' component.
i try to backport the gb.media component, but do not work, i
backported for squeeze, for wheeze and for lenny inclusivelly the
gstreamer 0.10.31 (all componentes, and packages) and compile with
lasted ffmpeg, codecs etc, all repository have amount (including
packages for that taks) 8Gb..
but gb.media do not compile and said requeriments for 3.4.X only need
gstreamer 0.10.30 as minimun, i have instaled, correctly packages and
backported base sgtremaer 0.10.31, and 0.10.19 bad plugins, etc etc
and do not enable the compilation
nobody care this due are focused in "lasted up to date moderm stuff"
I will backport the gstreamer1.0_1.0.1 from Quantal, and I will compile
Gambas with this. It's works.

Kendek
Tobias Boege
2013-11-15 14:28:55 UTC
Permalink
Post by PICCORO McKAY Lenz
Post by Willy Raets
it will run for at least 5 years in the production environment it is
being used. Why change what works just fine? Just because there is some
new fancy stuff out there?
i 'm running a payroll system in debian lenny, 24/7 at 365 days and
ther's no reason to "upgrade" to winbuntu 10000 or debian "unstable"
due are the "lasted"
u have right men! that's stupid! why changes if works perfectly!!!
Post by Willy Raets
Fact that gb.media will not run an a Ubuntu 12.04 is another of my
concerns. In production and personal environment I always stick to the
latest stable release (being 12.04 in buntu with a 5 year support cycle)
and this advise I also give to friends that I got onto linux.
This was cuase ddue benoit use "too moderm up-to-date ultimate release
version" of gstreamer
i'm tyred of the software always constant in "upgrades upgrades upgrades"
constant movement for support constant globalization! more upgrades
raises more requerimients so then more power to need so intel and amd
sell more and more
Yeah... Let's don't get political here.

(I don't want to sound like a sophist but I have to note this:)
English is not my native language but at least the normally used German word
for "development" means something around progress, kind of evolution. If you
don't want new packages to be used, then you effectively say that Gambas
should not be developed anymore by software developers but just maintained
by some bookkeeper. Then you will soon find people leaving the project. It
would just not be interesting anymore. (Well, at least then, Gambas would be
truly stable.)
Post by PICCORO McKAY Lenz
Post by Willy Raets
Why does Gambas need to depend on stuff that doesn't run on the latest
stable releases that are just 1 1/2 year out there and will be used for
several years to come.
Do we really need these hight dependencies when they only run on the
latest unstable releases (releases I only run the in VMs for testing
purposes and would never consider using in a production environment).??
Another case are that the typically response "upgrade to lasted, its
fixed there"
so then stable releases are not fixed?
Let's suppose we have a bug. What should we do about it? The normal
procedure is to fix it and then release a newer version. A newer
version is p.d. a more advanced state of the project. You can't have
a newer version of the project (with the bug fix) and at the same time
decry newer versions!

Of course I see that you mean two different things when you say "new" on the
one hand and "new" on the other hand but you should make it clear to not get
misunderstood.

Maybe what you want is something like this: have someone maintain an old
stable release of Gambas and just patch in bug fixes (like the Linux kernel
does) to these releases. You can even have someone to only patch in bug
fixes and interpreter enhancements and leaving alone gb.media at
gstreamer-0.10. Why not?

I tell you why not: you need people who volunteer (or someone who volunteers
to hire someone ;-)) and there currently is nobody to do it. Will you?

Regards,
Tobi

PS: I'm away over the weekend. I realise that I presented my views in a
rather destructive manner and as if they were facts - on purpose. If this
thread becomes a flame war about software development philosophies, sophists
and globalisation I just want to say: he started it :-) And in case it
matters: I use vim, not emacs ;-)
--
"There's an old saying: Don't change anything... ever!" -- Mr. Monk
PICCORO McKAY Lenz
2013-11-16 00:03:00 UTC
Permalink
Post by Tobias Boege
Yeah... Let's don't get political here.
PS: I'm away over the weekend. I realise that I presented my views in a
rather destructive manner and as if they were facts - on purpose. If this
thread becomes a flame war about software development philosophies,
sophists
and globalisation I just want to say: he started it :-) And in case it
matters: I use vim, not emacs ;-)
dont worry, its just u'r opinion..

but logic said: it when something works and just "the environment"
force to upgrade/change, this being illogical,
if something works it is illogical to change for something that
has not been tested yet! RIGHT?
Post by Tobias Boege
(I don't want to sound like a sophist but I have to note this:)
English is not my native language but at least the normally used German
word
for "development" means something around progress, kind of evolution. If
you
don't want new packages to be used, then you effectively say that Gambas
should not be developed anymore by software developers but just maintained
by some bookkeeper. Then you will soon find people leaving the project. It
would just not be interesting anymore. (Well, at least then, Gambas would
be
truly stable.)
well develoment its about progress, of course, today this meaning was
"misrepresented/twisted" in very convenient terms je!
i cited, its about progres TO A FINAL POINT!
not to a constant undefined no-end "upgrading way of things"
Post by Tobias Boege
Of course I see that you mean two different things when you say "new" on
the one hand and "new" on the other hand but you should make it clear
to not get misunderstood.
Maybe what you want is something like this: have someone maintain an old
stable release of Gambas and just patch in bug fixes (like the Linux kernel
does) to these releases. You can even have someone to only patch in bug
fixes and interpreter enhancements and leaving alone gb.media at
gstreamer-0.10. Why not?
I tell you why not: you need people who volunteer (or someone who
volunteers
to hire someone ;-)) and there currently is nobody to do it. Will you?
i doit that, my gambas packages has backported 12 patcheds from 3.5.X release

u'r opinion its a interesting point! of course
Post by Tobias Boege
"There's an old saying: Don't change anything... ever!" -- Mr. Monk
yeah .. ¬_¬u
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Tobias Boege
2013-11-17 16:47:32 UTC
Permalink
Post by PICCORO McKAY Lenz
Post by Tobias Boege
Yeah... Let's don't get political here.
PS: I'm away over the weekend. I realise that I presented my views in a
rather destructive manner and as if they were facts - on purpose. If this
thread becomes a flame war about software development philosophies,
sophists
and globalisation I just want to say: he started it :-) And in case it
matters: I use vim, not emacs ;-)
dont worry, its just u'r opinion..
but logic said: it when something works and just "the environment"
force to upgrade/change, this being illogical,
if something works it is illogical to change for something that
has not been tested yet! RIGHT?
Totally right. But you talk about your system. If you apply this statement
to Gambas, you say that we should stop making new components or adding new
features to existing ones. This is possible but some people out there want
new features - and, as I said, things would get boring around Gambas if we
didn't do new things with new libraries or newer versions of libraries.
Post by PICCORO McKAY Lenz
Post by Tobias Boege
(I don't want to sound like a sophist but I have to note this:)
English is not my native language but at least the normally used German
word
for "development" means something around progress, kind of evolution. If
you
don't want new packages to be used, then you effectively say that Gambas
should not be developed anymore by software developers but just maintained
by some bookkeeper. Then you will soon find people leaving the project. It
would just not be interesting anymore. (Well, at least then, Gambas would
be
truly stable.)
well develoment its about progress, of course, today this meaning was
"misrepresented/twisted" in very convenient terms je!
i cited, its about progres TO A FINAL POINT!
not to a constant undefined no-end "upgrading way of things"
Well, I'm a child of "today" and I grew up with this "undefined upgrading"
mentality, apparently. BTW, what would that "final point" be so we can work
straight towards it? (I'm currently, as university leaves time left, working
on a gb.inotify component. But I think this is OK since it doesn't need any
library.)
Post by PICCORO McKAY Lenz
Post by Tobias Boege
Of course I see that you mean two different things when you say "new" on
the one hand and "new" on the other hand but you should make it clear
to not get misunderstood.
Maybe what you want is something like this: have someone maintain an old
stable release of Gambas and just patch in bug fixes (like the Linux kernel
does) to these releases. You can even have someone to only patch in bug
fixes and interpreter enhancements and leaving alone gb.media at
gstreamer-0.10. Why not?
I tell you why not: you need people who volunteer (or someone who
volunteers
to hire someone ;-)) and there currently is nobody to do it. Will you?
i doit that, my gambas packages has backported 12 patcheds from 3.5.X release
u'r opinion its a interesting point! of course
Post by Tobias Boege
"There's an old saying: Don't change anything... ever!" -- Mr. Monk
yeah .. ??_??u
In the end, man is a pragmatist, isn't he? :-) You know, Mr. Monk changed
lots of things to please some higher need (to make things rectangular, for
example). :-)

I don't know how such things work with SVN but I'm sure you can have your
own branch of Gambas on sourceforge to make your "only bugfixes" Gambas
accessible to everyone else who doesn't want to depend on bleeding-edge new
libraries. In the end it's you who decides what Gambas your computer runs.

Regards,
Tobi
PICCORO McKAY Lenz
2013-11-17 17:04:41 UTC
Permalink
Post by Tobias Boege
Totally right. But you talk about your system. If you apply this statement
to Gambas, you say that we should stop making new components or adding new
features to existing ones. This is possible but some people out there want
new features - and, as I said, things would get boring around Gambas if we
didn't do new things with new libraries or newer versions of libraries.
yeah that's a pain constant for me and production environment...
Post by Tobias Boege
Post by PICCORO McKAY Lenz
i cited, its about progres TO A FINAL POINT!
not to a constant undefined no-end "upgrading way of things"
Well, I'm a child of "today" and I grew up with this "undefined upgrading"
mentality, apparently. BTW, what would that "final point" be so we can work
straight towards it? (I'm currently, as university leaves time left,
working
on a gb.inotify component. But I think this is OK since it doesn't need any
library.)
that's good example...
Post by Tobias Boege
I don't know how such things work with SVN but I'm sure you can have your
own branch of Gambas on sourceforge to make your "only bugfixes"
yeah! in my work i have own git clone of gambas from oficial, and we with
other patched it for estability..
Post by Tobias Boege
Gambas
accessible to everyone else who doesn't want to depend on bleeding-edge new
libraries. In the end it's you who decides what Gambas your computer runs.
we was providing a repository for debian releases but today domian end ans
i have no "dollars" for pay.. i swicht to lating hosting for pay in
bolivares
Post by Tobias Boege
Regards,
Tobi
Kende Krisztián
2013-11-17 18:19:45 UTC
Permalink
Post by PICCORO McKAY Lenz
Post by Tobias Boege
Totally right. But you talk about your system. If you apply this statement
to Gambas, you say that we should stop making new components or adding new
features to existing ones. This is possible but some people out there want
new features - and, as I said, things would get boring around Gambas if we
didn't do new things with new libraries or newer versions of libraries.
yeah that's a pain constant for me and production environment...
For example, I using the new "GB_GUI" environment variable. It's really
cool, I like this feature. And I like the exit codes (Quit N), this
feature has landed in the version 3.4. Maybe some of the new features
are needed in a production environment. Otherwise the development
environment is unsuitable to perform the task. And the developer
switches to something else.

Kendek
PICCORO McKAY Lenz
2013-11-18 14:29:16 UTC
Permalink
So then taking in considerations the newer features and changes so
developers and newer users must be notified in wiki and web page about
this, also notified about this in forums and related gambas how to's

by example all projects compiled/packages with 3.4.X must be
recompiled and re-packaged with newer 3.5.X revisions to work under
3.5.X and go

i noted this changes between 3.1 to 3.4, and 3.4 to 3.5
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Continue reading on narkive:
Loading...