So far we've completed step 1, (we've added lower-bounds to all requirements and have our check job verify such).
Next we need a co-availability (NOT installability) test for generated lower-constraints.txt. This means we will need a script to be extended to generate a lower-constraints.txt file and parse it line by line to check availability. This same script will be used by projects wishing per-project requirements.
Once that step is done we can start working with swift on getting them 'per-project'.
So far we've completed step 1, (we've added lower-bounds to all requirements and have our check job verify such).
Next we need a co-availability (NOT installability) test for generated lower-constrain ts.txt. This means we will need a script to be extended to generate a lower-constrain ts.txt file and parse it line by line to check availability. This same script will be used by projects wishing per-project requirements.
Once that step is done we can start working with swift on getting them 'per-project'.