On 10/22/06, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > On 10/22/06, André Detsch <[EMAIL PROTECTED]> wrote: > > Since 013 final is coming soon, its probably time for us to start > > compile official packages with Glibc 2.4. > > > > At this moment, packages at the official repository are all compiled > > against Glibc 2.3.2. Packages compiled with Glibc 2.4 (including most > > of the 013 packages) were kept separate, at > > http://rsync.gobolinux.org/013-packages/ > > The question is: how is the best way to perform this transition? > > > > Once one has Glibc 2.4 installed, old Glibc 2.3.2 based packages still > > work well, so I think it is be ok to keep the old packages at the > > official repository.
I'm not sure. Old packages have all sorts of problems (bad dependencies, bad Dependencies, etc.) and many are seriously outdated. The 013 store, in contrast, is much cleaner (wasn't it almost entirely built using ChrootCompile?) and doing this "reboot" of the store gives us the chance to increase the overall quality of our binary store to a new level. Sure, it would become much smaller, but now we have Compile (and ChrootCompile) which means we'll be able to fill up the binary store much more efficiently, I think. Also, one of my post-013 plans is to add full support for the rXpY recipe/package revision numbering scheme in scripts, so having a mostly new package store is a chance to 'restart clean' on that arena as well. We can keep the old package repository available with an "unsupported" status, not unlike like the "contrib" repo. > > The procedure for safely installing Glibc 2.4 in a exiting system is > > quite simple, but requires a small additional step: > > > > 1 - Become superuser > > # a superuser terminal has to be open before running step 2 > > # since you will not be able to perform 'su' or 'sudo' after step 2 > > and before step 3 > > 2 - InstallPackage Glibc--2.4--i686.tar.bz2 > > # there is no need to update any file inside the Settings directory > > 3 - cd /Programs/Glibc; mv 2.3.2 old_2.3.2 > > # a rm -rf could be performed as well, but having keeping a backup may > > be useful > > # if something goes wrong (having a live cd copy available might be > > also useful :) Interesting. Any idea why it is so? > > The most straightforward for us would be to ask users to perform this > > upgrade when willing to use newer packages, but I'm not sure how can > > we enforce this. Through dependencies. Once CheckDependencies is able to fetch its dependencies off the network separately from the package, we can make InstallPackage check dependencies before installing the package. If dependencies cannot be met, then the user will have to answer "y" to something like "This package requires Glibc >= 2.4 but you chose not to install it. Proceed anyway?" > Talking about Glibc, don't we need to instruct InstallPackage to take > them from the 013 store instead of the old one? I'm thinking about > letting it take into account /System/Settings/GoboLinuxVersion, using > the 012 store as a fallback. I know this is a bit later, but I forgot > about this topic until now. What do you think? I don't like the idea. In particular, GoboLinuxVersion does not say much (if anything) about the actual status of the system; dependencies is the way to go. -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
