>> Now fcron 3 has been already released. I'm not too much familiar with >> swup, but maybe there is the way to create fcron3 package which will not >> update fcron 2.* by default, but will override it if user runs "swup >> --install fcron3" manually? And let fcron 2 and fcron3 exist togeather >> like php4 and php5. Or is it a very large addition for stable release of >> TSL? CHT> Such a change can easily be done. I don't think they can co-exist, well, CHT> they can, but you need to rename a lot of files, like /etc/init.d/fcron3 CHT> etc. CHT> I suggest you prepare such a package for 2.2 community section, and when CHT> it's working, we'll just add it to that section for now. The general CHT> rule is that new packages should go into community section first, main CHT> distro later.
I mean they can co-exist in distributive, and not on machine under TSL. A user will have to decide if he wants to use fcron 2 or fcron3. I suggest the following scenario: - if a user wants to continue using fcron 2.9.5 with its bugs he does absolutely nothing. - if a user wants to jump to fcron 3, he does "--install fcron3", fcron3 package irretrievably overrides fcron2, and then --upgrade will cause an upgrade of fcron3 if available. As I remember some time ago sqlite3 was introduced almost the same way. For me it is pretty strange that TSL team does not want to do anything about such obvious bug of fcron 2.9.5. I don't see too much changes between 2.9.5 and the latest versions... Best regards, Denis Solovyov _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
