| 1 |
Hi David, |
| 2 |
|
| 3 |
thank you very much for answer. I will proceed this way. |
| 4 |
|
| 5 |
Regards, |
| 6 |
Jauhien |
| 7 |
|
| 8 |
On 01/11/2016 10:35 AM, David Grellscheid wrote: |
| 9 |
> Hi Jauhien, |
| 10 |
> |
| 11 |
> The package should certainly be called just Herwig from now on. I don't |
| 12 |
> know the Gentoo system well, but is it possible to do a transitional |
| 13 |
> meta-package Herwig++-3.0.0 that only has a hard requirement on |
| 14 |
> Herwig-7.0.0? This would help users with the transition. |
| 15 |
> |
| 16 |
> Thanks, |
| 17 |
> |
| 18 |
> David |
| 19 |
> |
| 20 |
> |
| 21 |
> On 03/01/2016 11:33, Jauhien Piatlicki wrote: |
| 22 |
>> Hi, |
| 23 |
>> |
| 24 |
>> Herwig 7.0.0 has been released recently: https://herwig.hepforge.org/ |
| 25 |
>> http://arxiv.org/abs/1512.01178. Its code base is a direct development |
| 26 |
>> of the Herwig++ code, but the name was changed to Herwig, as Herwig++ |
| 27 |
>> completely replaces old HERWIG now. |
| 28 |
>> |
| 29 |
>> The question is under what name should we package it now and how to |
| 30 |
>> proceed, so users get the expected updates? |
| 31 |
>> |
| 32 |
>> -- |
| 33 |
>> Jauhien |
| 34 |
>> |
| 35 |
>> |
| 36 |
>> |
| 37 |
>> _______________________________________________ |
| 38 |
>> herwig mailing list |
| 39 |
>> herwig@×××××××××××××××××.org |
| 40 |
>> https://www.hepforge.org/lists/listinfo/herwig |
| 41 |
>> |
Archives