1 |
2010-11-28 20:59:05 Zac Medico napisał(a): |
2 |
> On 11/28/2010 10:15 AM, Arfrever Frehtes Taifersar Arahesis wrote: |
3 |
> > 2010-11-19 16:51:03 Zac Medico napisał(a): |
4 |
> >> On 10/25/2010 06:24 AM, Arfrever Frehtes Taifersar Arahesis wrote: |
5 |
> >>> use.unsatisfiable and package.use.unsatisfiable files would cause that `repoman` would treat |
6 |
> >>> given USE flags in the same way as masked USE flags. These files wouldn't affect behavior of |
7 |
> >>> `emerge`: |
8 |
> >>> - If user has enabled given USE flag specified in use.unsatisfiable or package.use.unsatisfiable |
9 |
> >>> and if optional dependencies controlled by this USE flag are already installed or satisfiable, |
10 |
> >>> then `emerge` will allow to install given package. |
11 |
> >>> - If user has enabled given USE flag specified in use.unsatisfiable or package.use.unsatisfiable |
12 |
> >>> and if optional dependencies controlled by this USE flag cannot be satisfied (with current |
13 |
> >>> settings of ACCEPT_KEYWORDS, /etc/portage/package.keywords etc.), then `emerge` will print |
14 |
> >>> informative error message telling e.g. about a dependency masked by ~${ARCH} keyword. |
15 |
> >> |
16 |
> >> Can't we print a "masked by ~${ARCH} keyword" message as you suggest, |
17 |
> >> even without the use.unsatisfiable data? If so, then isn't |
18 |
> >> use.unsatisfiable redundant? Your patch [1] seems to behave exactly like |
19 |
> >> use.mask, so I don't see any value added. |
20 |
> > |
21 |
> > repoman sometimes needs to allow stable packages to have optional dependencies on unstable |
22 |
> > packages (usually until these packages are stabilized). My patch implements this functionality |
23 |
> > for repoman. |
24 |
> |
25 |
> It seems like you're trying to bypass an important function of repoman |
26 |
> though. The idea is that repoman is supposed to protect users from |
27 |
> experiencing unsatisfiable dependencies of this sort, and use.mask |
28 |
> accomplishes that. |
29 |
|
30 |
If "python_abis_2.7", "python_abis_3.1" and "python_abis_3.2" USE flags are masked using use.mask |
31 |
on given architectures until Python 2.7, 3.1 and 3.2 are stabilized on these architectures, then |
32 |
majority of reverse dependencies of Python wouldn't be tested with new versions of Python. |
33 |
|
34 |
Example {,R}DEPEND: |
35 |
python_abis_2.4? ( dev-lang/python:2.4 ) |
36 |
python_abis_2.5? ( dev-lang/python:2.5 ) |
37 |
python_abis_2.6? ( dev-lang/python:2.6 ) |
38 |
python_abis_2.7? ( dev-lang/python:2.7 ) |
39 |
python_abis_3.0? ( dev-lang/python:3.0 ) |
40 |
python_abis_3.1? ( dev-lang/python:3.1 ) |
41 |
python_abis_3.2? ( dev-lang/python:3.2 ) |
42 |
python_abis_2.5-jython? ( dev-java/jython:2.5 ) |
43 |
|
44 |
-- |
45 |
Arfrever Frehtes Taifersar Arahesis |