> > For example, in https://opensc.fr/jenkins/ the build on two windows > > platform depend-on and triggered-by the build on debian.
To build under Debian packages, we probably need: https://launchpad.net/jenkins.pbuilder.plugin pbuilder is the Debian chrooted package builder. If you allow us, we may trigger pbuilder on our farm using SSH. The problem with pbuilder is that it runs under root account (or sudo which is the same). So we will probably need to install a fresh server with all Debian and Ubuntu chroots. Builds will auto-sign packages. Priority should be set to zero, just like in Debian backports. I am guite disapointed by OpenSC-SM naming under Windows. From a user point of view, it should be more explicit and include a readable naming space, like for example name-year-date-32x.msi. Even if this means a single build everyday. Can we proceed with Debian stuff? We can cope with all GNU/Linux builds under all platforms including x32, x64 and ARM, providing signed packages and APT/RPMs repositories. Kind regards, -- Jean-Michel Pouré - Gooze - http://www.gooze.eu
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
