I'm going to play the role of the newbie here :P On Wed, Jun 11, 2008 at 10:14 PM, Moinak Ghosh <moinakg at gmail.com> wrote: > Hi Folks, > > Thought it is a good time to socialize what's up with work on the > 0.7.1 release. > Right now progress on the new website is a little slow with several of us > busy. > > I have built ON B90 and new FOX sources and using a base set of packages from > the existing BeleniX release I have created a chroot environment where > it is possible > to compile stuff.
I assume you mean that I could use any existing opensolaris / solaris setup (say build 81//belenix 0.7), follow your chroot instructions and then go about building somethin from a much later revision (build 90 in this case). Could you post the instructions for creating a chroot, please ? > I am currently building the SFW consolidation within > that chroot > environment. Subsequently I will be upgrading various packages in the BeleniX > spec files repository to newer versions and also upgrade to KDE 3.5.9 and > build > all of those. > One this to ensure would be that we use SFE where available. I'd recently spotted a minor issue where SFEwine had a dependency on SFWlcms. There was already an SFElcms on Belenix, but wine wouldn't build because SFWlcms was missing. I think the only way to spot such issues would be to build SFE on Belenix 0.7 once. Shive has been telling me this and I have started to follow this advice. > Once these things are done we will have a new set of packages using which I > can generate a new ISO and start testing it. I will also post a test > version of the > ISO for others to try out. > Ideally, with the steps taken to create all this. > We will be tackling the various bugs and RFE after all these builds are done. I'm wondering if moving from build 81 to build 90 is justifiable in a move from 0.7 to 0.7.1 It should be OK, of course, but it's just that the minor revision number change doesn't indiciate a a change in the underlying ON revision. > One of the things that people can help out with is to update the BeleniX spec > files to newer versions. Moinak, would it be OK to build within Belenix 0.7 itself, given that we're moving ON from build 81 to build 90. I faced a curious problem recently. On SXDE build 81, I was able to build and run vpnc 0.5.1. While I was able to successfully build vpnc on belenix 0.7 (based on build 81), I was unable to run it. There some issue with a missing "ip" command, I think. This is a separate topic, of course, but I want to ask if the following makes sense. - Build SFE end to end on Belenix 0.7 - Move to newer version where possible. Now here is where I get stuck. I could build stuff on Belenix 0.7, but the only way to validate that all this will work on build 90 would be to actually try it out on a build 90. And would that then be an early Belenix 0.7.1 that you would put out ? In which case, the following is what I can think of: - Take a prelim build 90 based 0.7.1 and build the SFE end to end on that. - Put out yet another 0.7.1 based on the revised packages and test again. > In additions new artwork like wallpapers, suggested > themes etc. are welcome. > Gilberto could play an important role here, I think. > One major work will be to build the slim_install repository and re-brand the > Caiman installer. This task is made difficult since most of the strings are > hardcoded and scattered all over the source files. Ideally these should all be > macros in a single header file. Can someone help with modifying Caiman > sources to collect all strings as macros in a single header ? The task should > be straightforward if a little tedious - maybe some scripting can help. We can > then submit a bug against Caiman and propose this patch on indiana-discuss. > This is important to allow other distros to easily re-brand Caiman and use it. > Sounds good. Pathches in the bug tracker seem to be the way to go :) > Finally GNOME 2.22 (JDS) will also have to be built. I will start pushing the > packages to the BeleniX package repository server as and when I have them > built. These will still be in the form of SVR4 packages installable via > pkg-get > as IPS work will take some time. > IMHO IPS still has a bunch of problems > and areas of improvement that need addressing before it can be generally > used. Lack of an on-disk format and mirroring are some things I personally > consider impt. limitations. > Well, given that one can still install pkgs on even opensolaris 2008.5, it seems fine that we stick to svr4 for now and pay attention to IPS some time later. No point in fixing IPS when Belenix itself needs out love and care ! > Of course I have missed or glossed over more work that needs to be done. > Some that I can think of: - Network repository - storage for sources mentioned in the spec files - Fixes to Belenix 0.7 such that it can build stuff. An important one that I can think of is the lsymlink from aclocal1.10 to aclocal > Regards, > Moinak. > _______________________________________________ > belenix-discuss mailing list > http://mail.opensolaris.org/mailman/listinfo/belenix-discuss > http://groups.google.com/group/belenix-discuss >
