I've looked at various options, including a config file setting and
various other methods but I think I will implement a 'em_make
--forceold' option which still checks the toolchain but allows em_make
to proceed with this warning:
if (($forceold == 1) && ($check eq "false"))
{
print "Old version of gcc detected in toolchain but '--forceold' used.\n";
print "This toolchain is not supported by emdebian-tools, some scripts\n";
print "may not function correctly.\n";
print "Packages built with this toolchain should not be uploaded to\n";
print "Emdebian repositories.\n";
$check = "true";
}
emsetup will be unchanged, running 'emsetup -s' will still indicate
that a newer toolchain should be installed or built with 'emchain'.
This has the effect that the new 'emsource' script will not be usable
with the unsupported toolchain - but this is intentional as emsource is
intended to make it easier to co-maintain packages destined for the
Emdebian target repositories. It simply wraps 'apt-get source' and 'svn
co $patchfiles' and creates the relevant tree structures beneath the
working directory. 'emsource' is an optional component of
emdebian-tools, packages that do not require co-maintenance will not
need to use it.
Comments?
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
Attachment:
pgp9ItAvuWEfz.pgp
Description: PGP signature