Can you have different patches to source code, according to different profiles? If so, then probably it's possible to do what you say.
Il 16/02/2016 20:57, Thorsten Glaser ha scritto: > On Tue, 16 Feb 2016, Luca Vercelli wrote: > >> I don't know what are "build profiles" :( > Then ask before thinking ;-) > >> however I dont' think so, > Mayyyyybe. With build profiles, you have something similar to > Maven profiles in that you can: > > • have different Build-Depends (on the debian/control side) > • generate less and/or different binary packages > • have different code (in debian/rules you can switch on a new > environment variable DEB_BUILD_PROFILES so you can use two > (partially or even completely) different recipes for building > while using the same source > > This is intended especially for bootstrapping and cross-builds: > you first compile with the bootstrap profile enabled, then do > whatever is needed to get the full profile working, then build > it without the bootstrap profile, superseding the bootstrapping > upload. (It’s intended that way, to be used to break dependency > cycles and bootstrap, not to flavourise packages inside just one > distribution… though I wish I could have a distro-specific default > profile so there were no delta between Debian and the-derivate- > which-cannot-be-named-from-Canonical any more, for one of mine.) > > bye, > //mirabilos
