According Yang Yi's suggestion, we still need to maintain syslinux in devel:tools:building and Tools:Building currently. But for the clarity of MeeGo syslinux, we will maintain it separately, as before we did. The new requests will be sent out ASAP, with the latest version 4.04.
Thanks - jf.ding On Wed, Jul 13, 2011 at 06:09:36AM +0800, Ding, Jian-feng wrote: > Anas, > I don't know the old hybrid ISOs problem, but from current mic2 code. I also > find > we need not maintain syslinux in tools projects now. > So we should remove it from devel:tools:building and Tools:Building, and > cleanup > its spec file in MeeGo projects. > Is it ok? > > - jf.ding > > On Wed, Jul 13, 2011 at 06:06:23AM +0800, Nashif, Anas wrote: > > > > > > On Tue, Jul 12, 2011 at 6:08 PM, Kok, Auke-jan H <[email protected]> > > wrote: > > > > On Tue, Jul 12, 2011 at 12:16 AM, Nashif, Anas <[email protected]> > > wrote: > > > On Tue, Jul 12, 2011 at 7:12 AM, Jian-feng Ding > > <[email protected] > > > > > > wrote: > > >> > > >> Auke, > > >> Because the syslinux is maintained in devel:tools:building, which > > need > > to > > >> support many > > >> distros other than MeeGo. Just like mic2 and spectacle, etc. > > >> > > >> - jf.ding > > > > > > I doubt the distros we want to support do not support syslinux, is > > there > > a > > > reason why we want to force our version of the package on other > > distros? > > > > It also sounds like a recipe for trouble to replace e.g. SuSE's > > bootloader with a half-baked MeeGo version. > > > > I can understand having a sane fallback version in the tools repo, but > > then that shouldn't be the version we have in MeeGo. We really need to > > push the btrfs features in 4.04 into MeeGo for instance... > > > > The best solution seems to just drop syslinux from devel:tools and > > maintain a non-conflicted syslinux for MeeGo only. We definately don't > > want unintended consequences from e.g. non-MeeGo changes to syslinux > > affecting all MeeGo systems. Remember that this is a bootloader, not > > just some random development tool. > > > > > > Yes, agree. If I remember correctly, the only reason we added syslinux back > > then was the support for hybrid ISOs few years back. Status of syslinux and > > other tools needs to always be evaluated in the tools repo and when > > something > > is not needed anymore it needs to be removed and the distro version needs > > to be > > used. > > > > Anas > > > > > > > > Auke > > > > _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
