Martin,

On Jul 21, 2015, at 5:57 AM, Martin Gerhard Loschwitz 
<[email protected]<mailto:[email protected]>> wrote:

Pedro,

Am 16.07.2015 um 21:01 schrieb Pedro Marques 
<[email protected]<mailto:[email protected]>>:

Filip,

On Jul 16, 2015, at 6:47 AM, Filip Pytloun 
<[email protected]<mailto:[email protected]>> wrote:

Hello Martin,

so is there some repository that you use to track packaging changes when you 
don't contribute back to Juniper/contrail-packages?
I didn't found such repository or any more informations on how syseleven builds 
are done, so that was the main reason why we have chosen to use 
Juniper/contrail-packages to build packages and contribute back to it.

Are your changes and restructuring so huge or incompatible so they can't be 
contributed back to Juniper/contrail-packages?

There are probably the following categories of changes:
1. Migrating third-party downloads to a set of x-dev packages.
2. Choice of init systems (supervisor, systemd, initd).
3. Details that may depend on deployment design.

AFAIK,
In order to solve 1. we just need someone to upload the packages to the 
opencontrail PPA so they can be used as build dependencies; it would be good to 
have the packaging scripts committed to contrail-packages also so that these 
source packages can be recreated. This just means adding packages… Once this is 
done, the opencontral CI systems need to be modified so that they can use the 
PPA as a repository in order to download these files… then the build 
dependencies can be added. It is a sequence of steps requiring coordination but 
it not really a design issue.


I did upload the required packages for Ubuntu to the Launchpad repo and sent in 
patches that
would remove the third_party-stuff.
They failed to be build because they won't work on Fedora
obviously if the packages aren't there as well.

We need to leave the third-party stuff in place in order to support RHEL 
builds, but not use it in debian builds.
For that it is only necessary that the source package doesn’t include the 
third-party directory as it does today.

Since then, I didn't hear anything else about it.
What is the story on these? We need a working set of dependency packages for 
all currently
supported distributions before we can go ahead and delete third_party from the 
build process
properly.

We can just stop using third-party for debian builds. The third-party script 
has an annotation that makes the packages that are downloaded platform 
dependent.

  Pedro.
_______________________________________________
Dev mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Reply via email to