Re: Bootstrapping OpenPKG-4.0b81 fails
For OpenPKG I in the meantime will just disable the whole mkdtemp stuff as it is currently not used at all. OpenPKG 4.0b82 and above will have this fixed. Ok, openpkg-4.0b84-20090920 now builds fine. Now let's see if OpenPKG is of any use for me. ;-) Thanks, Stefan __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Project status/future
Hi there. 1) After playing around a little with OpenPKG I'm wondering about this projects status. The last (official) release is dated from 2007-12-27, quite a lot of pages at openpkg.org are outdated and the mailings list seem to be rather quiet. All this gave me the impression that this project is about to fade away. Is that correct? 2) The FAQ states that someday OpenPKG might support dynamically linked (internal) libs. Are there any news on that? Bye, Stefan __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: Project status/future
On Mon, Sep 21, 2009, Stefan Palm wrote: 1) After playing around a little with OpenPKG I'm wondering about this projects status. The last (official) release is dated from 2007-12-27, quite a lot of pages at openpkg.org are outdated and the mailings list seem to be rather quiet. All this gave me the impression that this project is about to fade away. Is that correct? No, OpenPKG certainly is not fading away. We were just too busy with other earn-a-living jobs and OpenPKG 4.0 was still not ready until recently. Hence we kept the websites around until we have something new. Now that OpenPKG 4.0 is stable and already working on lots of production servers, it will be officially released soon -- together with a new website. That the last official bootstrap is from 2007-12-27 was intentionally, as this was the last time we updated the old RPM 4 based bootstrap. Since this time we worked on the RPM 5 based one for OpenPKG 4.0. 2) The FAQ states that someday OpenPKG might support dynamically linked (internal) libs. Are there any news on that? No, not worth the effort as even in the days of GNU libtool it is an endless effort when it comes to true cross-platform solutions like OpenPKG. And beside faster updates in case of security issues (because you don't have to rebuild the application) there is no real advantage in practice. The disadvantages (portability issues) fully destroy the advantages. Ralf S. Engelschall r...@engelschall.com www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: Project status/future
On Sep 21, 2009, at 3:41 PM, Ralf S. Engelschall wrote: No, not worth the effort as even in the days of GNU libtool it is an endless effort when it comes to true cross-platform solutions like OpenPKG. And beside faster updates in case of security issues (because you don't have to rebuild the application) there is no real advantage in practice. The disadvantages (portability issues) fully destroy the advantages. What's the actual engineering issue with dynamic vs static? Is it just that there's too many flavors of dynamic linking? Just curious, not questioning at all. 73 de Jeff __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
