Hi,
On 10/21/2011 04:05 PM, ext Carsten Munk wrote:
That said - if you keep the source packages in sync (as OBS can do)
and map a x86 version instead of ARM version of each
interpreted-language-extension through SB2 mapping, it might work.
...
> But a definite no to a tools distribution that we map to that's not
> updated so often. It's a maintainability nightmare. Packages that are
> being built should be built using tools that are from the OS they're
> being built for or we're in for a world of hurt.
IMHO developer tools should be stable, you update them only
at some specific points. Not so that if somebody happens to
upload e.g. a latest GCC or Qemu snapshot to a repository,
that's immediately being used to build everything else.
Also, everybody should be using the same versions of the tools
(unless they're testing tools upgrade) otherwise debugging their
problems becomes an impossibility.
I.e. OS may have several versions of a given tools package, but
which one is actually used for building the software should be
carefully tested/selected[1], otherwise you're in a world of hurt.
Debugging compiler code generation issues is one of the less
easy things, especially if you've happened to propagate that
mistake also into some other (arm or x86) tools package where
that mis-compile will first appear...
- Eero
[1] For GCC upgrades I would say that this testing takes months
rather than weeks.
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
