| 1 |
Neil Bothwick wrote: |
| 2 |
> On Sun, 15 Jun 2014 00:10:41 -0500, Dale wrote: |
| 3 |
> |
| 4 |
>> Ahh. I was curious and thought about that. That version is mentioned |
| 5 |
>> in the error tho so I wasn't sure. I wonder tho, can I add that file |
| 6 |
>> and not have a version at all? Sort of like I do in package.keywords |
| 7 |
>> etc etc. |
| 8 |
> |
| 9 |
> You can, but you just said. |
| 10 |
> |
| 11 |
>> I've |
| 12 |
>> never put anything in the env directory before and would prefer to keep |
| 13 |
>> it that way because I will forget it is there and it will come back and |
| 14 |
>> bite me some day. |
| 15 |
> |
| 16 |
> Using the version number means the setting will "expire" when the |
| 17 |
> package is upgraded, meaning it won;t be able to bite you later on. |
| 18 |
> |
| 19 |
> Though I would prefix the atom with ~ instead of = to cover patch level |
| 20 |
> updates. |
| 21 |
> |
| 22 |
> |
| 23 |
|
| 24 |
I have looked for a place where it is documented how to do that. I know |
| 25 |
there is a lot of ways to add packages to those files with <=> and such |
| 26 |
in front of the package names. Do you have a link to some docs on |
| 27 |
that? If not, some examples would be cool. |
| 28 |
|
| 29 |
Well, I was going to try adding the variable to make.conf as posted in |
| 30 |
another email. I think that may be better since this seems to be a |
| 31 |
issue that is "in flux" at the moment. ;-) |
| 32 |
|
| 33 |
Dale |
| 34 |
|
| 35 |
:-) :-) |
| 36 |
|
| 37 |
-- |
| 38 |
I am only responsible for what I said ... Not for what you understood or |
| 39 |
how you interpreted my words! |
Archives