It is time for a new release of Pike 7.6. Is there anyone who can do the release notes? If not, we'll just wait a bit longer...
On Fri, 22 Jul 2005 20:45:05 +0000 (UTC) "Martin Nilsson (DivX Inc.) @ Pike (-) developers forum" 10353@lyskom.lysator.liu.se wrote:
It is time for a new release of Pike 7.6. Is there anyone who can do the release notes? If not, we'll just wait a bit longer...
There are a few problems with Pike 7.6 in CVS building on openbsd. It would be great if they could get fixed before rolling a new release. They aren't major, just some configure checks needing extra libs and such, but I don't know much about autostuff to submit patches.
I recently started going through the entire config.log for pike and all the base modules I can install the dependancies for to look for openbsd specific issues, and I'm almost done, so I can get a full list if anyone is willing to look at it.
Adam
i just read the whole changelog. there are only 166 entries, (after condensing the log with cvs2cl)
most are small bugfixes (commented as such) backports of fixes in 7.7 typos a few fixes for reported bugs and only a few things with a longer description
nothing really substantial for release notes, or at least, i can't see anything substantial other than making a statistic...
greetings, martin.
well, I know of at least 2 bugfixes that impact applications I work with. There may not be major new functionality (at least I'd hope not for an incremental release). It would be good form to list out what those changes are. I can work on it monday if no one else starts before then.
Bill
On Jul 23, 2005, at 11:34 AM, Martin Bähr wrote:
i just read the whole changelog. there are only 166 entries, (after condensing the log with cvs2cl)
most are small bugfixes (commented as such) backports of fixes in 7.7 typos a few fixes for reported bugs and only a few things with a longer description
nothing really substantial for release notes, or at least, i can't see anything substantial other than making a statistic...
greetings, martin.
On Sat, 23 Jul 2005, H. William Welliver wrote:
well, I know of at least 2 bugfixes that impact applications I work with. There may not be major new functionality (at least I'd hope not for an incremental release). It would be good form to list out what those changes are. I can work on it monday if no one else starts before then.
Bill
Another that might not be as high a priority is that a lot of new distributions (linux mainly) are only delivering with gtk2, not with gtk1.2 anymore. For example, with Fedora Core 4, the GTK module that pike 7.6.24 comes with won't be installed, because the appropriate libraries are not installed.
So, the new GTK2 module should be included, I believe.
Yes, I did write the module, so I have sort of a vested interest in it being included, but I was thinking of upgrading my desktop to FC4, but since I have some GTK applications, I need to have a pike version that supports GTK on that platform, which means the new GTK2 module.
Granted, the GTK2 module needs a little work to be appropriate for inclusion, but that is just one thing I can think of.
On Sat, Jul 23, 2005 at 01:58:17PM -0500, Lance Dillon wrote:
So, the new GTK2 module should be included, I believe. Yes, I did write the module, so I have sort of a vested interest in it being included
have you asked for write access to the pike repository yet?
would be nice to see gtk2 in 7.7 soon.
btw, you don't seem to be using SWIG to generate the interface. this will make it harder to maintain compatibility to changes in the gtk2 api. with SWIG they could be updated with a lot less work.
greetings, martin.
Correct me if I'm wrong, but does not SWIG suck? I.e. passing around opaque "pointers" instead of using object orientation etc.
At least it did a couple of years ago. I was recommended to use it for integrating a lib with Pike but was utterly discusted and did the glue manually instead.
On Wed, 2005-08-17 at 09:10 +0000, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
Correct me if I'm wrong, but does not SWIG suck? I.e. passing around opaque "pointers" instead of using object orientation etc.
After it was mentioned, I looked at it, but I saw that it wasn't appropriate. SWIG doesn't keep track of library interfaces such as gtk2, but the language interfaces, such as pike or python or whatever. So, if the gtk2 library api changed, I would still have to change the files; it wouldn't fix that problem. Some other things I do in the module also makes it difficult to apply in this situation, also, such as the object orientation, of which there is a lot in the gtk2 module.
pike-devel@lists.lysator.liu.se
-
Adam Montague -
Fredrik (Naranek) Hubinette (Google) ＠ Pike (-) developers forum -
H. William Welliver -
Lance Dillon -
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum
-
Martin Baehr -
Martin Bähr
-
Martin Nilsson (DivX Inc.) ＠ Pike (-) developers forum
-
Peter Bortas ＠ Pike developers forum