1 |
On Tue, Sep 15, 2015 at 2:07 AM, Paweł Hajdan, Jr. |
2 |
<phajdan.jr@g.o> wrote: |
3 |
> On 9/14/15 9:13 AM, konsolebox wrote: |
4 |
>> On Mon, Sep 14, 2015 at 2:29 PM, Paweł Hajdan, Jr. |
5 |
>> <phajdan.jr@g.o> wrote: |
6 |
>>> On 9/14/15 6:35 AM, konsolebox wrote: |
7 |
>>>> Many times we need to match packages like this: |
8 |
>>>> something-1.0.2a.* |
9 |
>>> |
10 |
>>> Could you give specific examples, i.e. what packages, what |
11 |
>>> dependencies, why is that needed? |
12 |
>> |
13 |
>> For accuracy and peace of mind regardless of how often conflicts |
14 |
>> could happen. |
15 |
> |
16 |
> I agree =pkg-4.1* also matching pkg-4.10 is a concern. |
17 |
> |
18 |
> In that case though, it would change the focus of the discussion to how |
19 |
> * operator should work, not necessarily adding a new ~> operator. |
20 |
|
21 |
Here are my issues if we try to modify =* and not add another operator: |
22 |
|
23 |
1) We'll completely abandon having an operator that matches the |
24 |
remaining parts of a version number for good: =cat/foo-5.2015* would |
25 |
no longer work. |
26 |
|
27 |
2) We'll have to decide if we should remove the leading zeros of a |
28 |
version number: should 5.01.0 and and 5.1.2 be the matched the same if |
29 |
I used =5.01*? We can only either allow it or not. We keep one |
30 |
feature, we lose the other feature. If we use another operator, |
31 |
=5.01* could just stay strict on matching 5.01*, whereas the operator |
32 |
could have the function of treating them like decimals instead. We |
33 |
can keep =* have the string matching feature while have another |
34 |
operator do the more-on-arithmetic one. |