Mozy Online Backup: 2GB Free. Automatic. Secure.
Subject: Separate mailing lists for gpa? - msg#00002
List: encryption.gpg.gpa.devel
Hi,
since a while gpa has a nice new infrastructure at
http://wald.intevation.org/projects/gpa/ .
Wouldn't it make sense to create there the mailing lists
"gpa-users" and "gpa-devel" for the respective discussion groups.
This might be a chance to generate more noise, ie. to be more
attractive to get in contact. gpa-dev@xxxxxxxxx probably has
too unclear objectives?
Best
Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Upgrade gpa from GTK+ 2.2 to 2.4?
Hi gpa developers,
I wonder whether there is any reason not to upgrade the minimum version
of GTK+ 2.2 to 2.4. With 2.4 various new interesting methods have been
introduced.
Getting rid of any deprecated methods is also interesting, I guess.
Or is even GTK+ 2.6 something we can assume to be everywhere where gpa
aims for?
Best
Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de
Next Message by Date:
click to view message preview
Re: Upgrade gpa from GTK+ 2.2 to 2.4?
At Tue, 21 Nov 2006 23:40:01 +0100,
Jan-Oliver Wagner wrote:
>
> Hi gpa developers,
>
> I wonder whether there is any reason not to upgrade the minimum version
> of GTK+ 2.2 to 2.4. With 2.4 various new interesting methods have been
> introduced.
I have no objection; however, such a bumb should be done when the new
methods are actually used (ie, ideally, the minimum required version
should reflect the minimum actually required version).
> Getting rid of any deprecated methods is also interesting, I guess.
> Or is even GTK+ 2.6 something we can assume to be everywhere where
> gpa aims for?
Again, the minimum required version should be motivated by actual
changes in the code base.
Currently, we build gpg4win against glib 2.9 and gtk 2.6. As such I
have no objection to go up to there, assuming the windows port of that
version is complete with respect to the features you want to use.
Beyond that (say, 2.8), more testing would be required if the new
version compiles and runs correctly on Windows.
Gtk 2.8 was released over a year ago, so we can go even up to that.
It seems to be the current stable version in use in distributions
(Ubuntu Drapper for example). The limiting factor is the Windows
port.
Thanks,
Marcus
Previous Message by Thread:
click to view message preview
Upgrade gpa from GTK+ 2.2 to 2.4?
Hi gpa developers,
I wonder whether there is any reason not to upgrade the minimum version
of GTK+ 2.2 to 2.4. With 2.4 various new interesting methods have been
introduced.
Getting rid of any deprecated methods is also interesting, I guess.
Or is even GTK+ 2.6 something we can assume to be everywhere where gpa
aims for?
Best
Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de
Next Message by Thread:
click to view message preview
Re: Separate mailing lists for gpa?
On Tue, 21 Nov 2006 23:39, jan@xxxxxxxxxxxxx said:
> This might be a chance to generate more noise, ie. to be more
> attractive to get in contact. gpa-dev@xxxxxxxxx probably has
> too unclear objectives?
Agreed. I don't know for what gpa-dev should actually be used for.
In the past we used it for Aegypten related stuff. Now that GnuPG 2.0
has been released the regular GnuPG mailing lists are better suited
for this. Even the extra tools like dirmngr and pinentry have their
place there because they are closely related to GnuPG.
Thus we might even thinking of closing gpa-dev and moving existing
users over to another lists. That list should then be used for GPA -
in the sense of gpa-x.y.z.tar.bz2. I don't know whether a user and a
developer list is justified. gpa-users@xxxxxxx is probably sufficient
for now.
Salam-Shalom,
Werner