Re: [gccsdk] Recommended autobuilder/packages/etc distros

In message <537BAB40.6080304@sky.com>
Lee Noar <leenoar@sky.com> wrote:


>
> If I'm reading the fetch-program script correctly, it looks in testing
> (jessie) first and if it doesn't find the package there, falls back to
> stable (wheezy).
>

Linux distros by default only use one level of packages, I can recall
ruining a Debian install by installing newer packages.
I realise a lot of times, it will work.
I think it would be simpler if the autobuilder defaulted to stable
(wheezy until 2015) and if testing is required the overiding could be
done with AB_URL in any setvars filer.

At the moment, results from autobuilder can vary because if a download
is not successful it will go to the alternative branch, and one person
can get different errors to another, which makes bug reporting
complicated. Debian testing (jessie) wont be frozen until November,
and security updates are only guaranteed for the stable branch,
So it makes me wonder why we use testing by default?
I realise some packages just aren't available yet in stable but
couldn't they be dealt with case by case?

What worries me is if the combination of branches packages doesn't
throw an error when building/linking but then causes the end
binary to error.

If we are moving to newer GCC, would it not be worthwhile to have
everyone installing from the same branch for the purpose of
bug reporting?

I am a relative newby so feel free to correct me on this thing
that has always puzzled me.

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK