IPS update is being worked on. However, I found out that my build environment is messed in a mysterious way. I am sick, so everything I am working on has stalled (sorry, health first). IPS will be definitely updated as I want python 2.7 in the tree and make it default at some point.
Speaking of creating ISO image, it's up to you then. However, I think that we should choose a deadline for changes to be integrated into oi-userland. If that deadline passes, we simply create ISO images. If we know that some integrated changes might break something seriously, we simply skip that until it's get fixed (this might satisfy people, who want stable hipster, which I consider nonsense at this stage). What do you think? Cheers, Adam On Oct 17, 2013, at 7:49 AM, Alexander Pyhalov <[email protected]> wrote: > Good morning, Adam. > > Adam Števko писал 17.10.2013 08:58: >> Hi, >> let's push the fix and also recreate iso, something like Q3 ISO >> release of hipster. >> Anything against this idea? >> Adam > > I've thought about creating ISO a bit later - when PHP work and Net-SNMP > update is finished. > To finish it I need 64bit libwrap (I sent a RTI yesterday) for php-tcpwrap > extension (currently missed in PHP 5.4) > and real fix for this bug (I think the fix is coming soon). > However, I would also like to have gcc-compiled PostgreSQL (8.4 and 9.3) and > so on and so on. > I think I'll never stop to wish more (for example, I'm craving for IPS update > and python 2.7 :)). > So, let's push the fix and recreate ISO. > At least the latest ISO was released two months ago. > Since then we have a rather good portion of new software and some critical > fixes in GCC toolchain. > > --- > System Administrator of Southern Federal University Computer Center > > > > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
