[tao-users] Debian 8 production.
SKRZYNIARZ Alexandre
alexandre.skrzyniarz at fr.thalesgroup.com
Tue Feb 9 03:26:50 CST 2016
Hi,
On 02/08/2016 11:32 AM, Pau Garcia i Quiles wrote:
> Hello,
>
>
> In addition to the renamed files (which is not a bug), Alexandre's patch
> re-enables TAO.
I fact, that was the whole point.
We need tao for one of our product. As TAO build is deactivated, users
need either to build ACE/TAO manually, or to update the debian build.
>
> We (the Debian developers maintaining ACE and TAO) had to disable the
> build of TAO due to licensing problems. To get TAO back in Debian, we
> need to split the ACE+TAO source package and build in two parts: ACE
> stays in main, TAO goes to contrib. Problem is that requires quite a lot
> of time and neither Thomas Girard nor I can do that in our spare time,
> or convince our employers to do that for free. Unless someone does the
> work or finances it, it may take a good while to get TAO back to Debian
> proper :-(
>
So, if I understand well, if we cannot work on source splitting, we have
the following choices:
1) fix the licensing problem. I guess that if it is not fixed yet, there
is some complex issues involved.
2) I don't know if this is acceptable from a Debian Policies point of
view, but can we move the ACE/TAO source package to contrib, and build
binary packages that goes either in main or contrib from it? That would
prevent the need to split the sources.
3) Downgrade ACE from main to contrib. Therefore, no source splitting
would be necessary. I'm not sure of what would be the consequences for
main packages that depend on ace packages.
4) Ship my patch as it is in the ACE/TAO distribution with some
documentation for deployment, so that end users can build their own
packages with ease if they need tao debian packages.
What are your thought about that?
--
Alexandre SKRZYNIARZ, PhD.
THALES AIRBORNE SYSTEMS
10 Av 1ere DFL, 29200 BREST, France
email: alexandre.skrzyniarz at fr.thalesgroup.com
More information about the tao-users
mailing list