----- Original message -----
btw, personally I don't think it is good solution as Moblin image is so big
at GB level and I'd recommend starting from much smaller one like Maemo and
"enrich" it.
Even more important; scrap the idea of changing from deb to rpm. What on earth
were they smoking when they made that decsion!
this doesn't really help the discussion at all.
the decision to stick with rpm was made inside smoke-free buildings.
It seems the .rpm format allows to include special distribution licenses while
the .deb don't. Both formats are very good and IMHO will be great if we see the
.deb used for core distribution packages (OS) while .rpm handles third party
apps and contributions.
Krohon
Speaking from personal experience, there are deb-derived package formats (e.g
ipkg) intended for embedded devices but the standard one isn't really
appreciably
different from rpm in terms of space consumption - once the assumption is that
the device contains a complete package database of what's on the device, you
get what you get, which is a fair bit of "bloat".
As I've said elsewhere, there's kind of a divide between "stuff in the distro's
repository" and "stuff outside", and rpm vs. deb doesn't really end up being
the major issue here, the major issue is whether a package that's essentially
outside ("third party app") needs to depend on the internal details of the
particular version of the particular repository. I've not been convinced any
of the efforts at more independent packaging have done better than rpm/deb
for third-party. but there are lots of folks who disagree. And for internal,
as long as things are self-consistent, it doesn't seem to matter a whole lot,
if you take the body of what rpm/deb do/don't support there's far more in
common than different.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
