Pike-devel May 2004

pike-devel@lists.lysator.liu.se

11 participants
65 discussions

License question for contributed source
by Dan Nelson 13 May '04

13 May '04

I want to replace Array.dwim_sort_func with the C function at http://www.sourcefrog.net/projects/natsort/ ; it's much faster than the current Pike implementation, but is under the zlib license. I believe it's compatible with GPL/LGPL/MPL, but would like to be sure before I submit my patch. www.gnu.org explicitly says zlib is compatible with the GPL. -- Dan Nelson dnelson(a)allantgroup.com

5 6

mprotect
by Martin Nilsson (r�fsfiskal) ＠ Pike (-) developers forum 13 May '04

13 May '04

Grubba, could you elaborate how mprotect(2) is broken in Linux?

2 1

Re: pike 7.4 port and FreeBSD
by Xavier Beaudouin 13 May '04

13 May '04

Le 12 mai 04, à 17:23, Kai Voigt a écrit : > Xavier Beaudouin wrote: >>> that's fine for me. I wasn't able to run Roxen on top of Pike 7.4 >>> with >>> a working freetype2 support. Pike 7.6.66 was compiling easily and I'm >>> looking forward to have a port in /usr/ports/ soon. >> >> pike 7.6.6 is in /usr/ports/lang/pike76 :-) >> >> So just do a little cvsup for your port-supfile and you'll get it :) > > I'm already building the port with my required options. Then I will > replace > my manually installed Pike 7.6.66 to see if everything still works out. > >> Enjoy and make me some feedback if you have some ! > > Will do in a second. If it's running, I can try to build a Roxen > 4.0-cvs > port on top of your Pike port. I guess this would be a nice idea since > my > last port was Roxen 2.1.something :-) Should be a good idea :) /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

1 0

autodoc and xslt
by Bill Welliver 13 May '04

13 May '04

Has anyone done any work using XSLT to present joined and assembled AutoDoc xml files to a web browser? I'd like to not have to have little trees of html documents laying around, and would prefer to just transform the xml data into a web page. Any thoughts about how to do this? I'm sure it would be pretty simple for someone versed in XSL(T) and such. Bill

2 1

GTK in pike
by Martin Nilsson (r�fsfiskal) ＠ Pike (-) developers forum 13 May '04

13 May '04

I think the correct dll:s are in one of the 7.4 windows betas. Try install them first and then the latest one. I think it is enough to install ftp://pike.ida.liu.se/pub/pike/beta/7.4.11-20030101/ but if my memory fails my just try the next one :) Note to everyone: We should make a new 7.4 dist soon. This isn't the first time this issue has appeared. / Martin Nilsson (räfsfiskal) Previous text: >2004-05-10 19:15: >Subject: GTK in pike >-------------------------------------------------------------------- >Yes, I get an empty array, but gtk-1.3.dll that came with the >distribution is in the binary folder. > >> GTK library is missing or incompatible > >Well, it's all from the same recent download (Pike export stamp >time:1077723810 major:7 minor:4 build:44 year:2004 month:02 >day:25 hour:15 minute:43 second:30) > >What to do? > >Thx >Hans > > > > > / Brevbäraren >

2 1

Re: pike 7.4 port and FreeBSD
by Xavier Beaudouin 12 May '04

12 May '04

> that's fine for me. I wasn't able to run Roxen on top of Pike 7.4 with > a working freetype2 support. Pike 7.6.66 was compiling easily and I'm > looking forward to have a port in /usr/ports/ soon. pike 7.6.6 is in /usr/ports/lang/pike76 :-) So just do a little cvsup for your port-supfile and you'll get it :) Enjoy and make me some feedback if you have some ! /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

1 0

pike 7.4 port and FreeBSD
by Xavier Beaudouin 12 May '04

12 May '04

Hello there, Since pike 7.6 is out (and mostly usable.... !), I have asked freebsd portmanagers to remove pike 7.4 from freebsd ports. You may think it is strange, but there is nothing that runs on 7.4 from the Caudium Group and maintaining 7.4 on FreeBSD is a fscking pain in the ass... :( Note that this doesn't notice that pike 7.4 is not usuable on freebsd, but make it up to date and compliant with freebsd port manager rules is really too difficult. Main problem is pthread compliance library selection that cannot be handled with 7.4, until pike 7.6/7.7 autoconf "--with-threads-lib" parameter be backported... /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

1 0

License question for contributed source
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 10 May '04

10 May '04

Incorrect; the proposed version also treats leading spaces differently for numbers, similar to how leading zeroes already work in dwim_sort. For example, "pic4" < "pic 4" < "pic04". Otherwise they seem to do the same thing already.

2 2

Docs branching/tagging?
by Alexander Demenshin 09 May '04

09 May '04

Hi everybody, What about branching (or tagging) at least online docs (available on Pike's site), so that every particular change/feature/desription will not float in air? I mean, currently there is no way to distinguish which feature is implemented in which version, and if there will be some indicators (like "Added in 7.7) it would be a bit better... Or, perhaps, just splitting online docs into two (7.6/7.7) would do the trick? PS: Should I expect that everyone will suggest me to install local copy of docs instead? :) Regards, /Al

5 5

change log
by Bill Welliver 09 May '04

09 May '04

OK, now that 7.7 is open for business, how about a "rule" that developers that add or change functionality worth noting should add a description of the change to the change log file? For the record, this is _not_ the same as a cvs change log entry in that not every checkin will be reflected in the change log document. The caudium project has a rolling change log that might be worth looking at for inspiration. Does anyone have any opposition to the idea? Bill

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel May 2004