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. Auke _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
