Changes between Version 3 and Version 4 of WikiStart/Toolchain/Flavors


Ignore:
Timestamp:
08/15/11 16:47:12 (8 years ago)
Author:
sylvain.joyeux
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart/Toolchain/Flavors

    v3 v4  
    9494= For reference: branch-based handling = 
    9595 
    96 Another scheme has been initially tried. In this scheme, the root autoproj configuration would be common, but the package sets would be setup on a per-flavor basis and loaded using the $FLAVOR branch. 
     96Another scheme has been initially tried. In this scheme, the root autoproj configuration would be common, but the package sets would be setup on a per-flavor basis and loaded using the $ROCK_FLAVOR branch. 
    9797 
    98 The main issue with that scheme is that it is *very* hard to mix flavors: as soon as one is using the "next" flavor of the rock package set, he does not have access to the packages that are only defined in "master". The advantage, obviously, is that the  
     98The main issue with that scheme is that it is '''very''' hard to mix flavors: as soon as one is using the "next" flavor of the rock package set, he does not have access to the packages that are only defined in "master". The advantage, obviously, is that it is in principle not possible to break next by breaking the autobuild configuration (since the next autoproj configuration changes only during the updates of next). 
    9999