| 1 |
Hi Per. |
| 2 |
|
| 3 |
Please take a look at dev-lang/smarteiffel ;) and #8897. |
| 4 |
The first issue is taken care of by using already renamed source. Please take |
| 5 |
a look at the ebuild to see how was second one resolved as well as some more |
| 6 |
stuff... |
| 7 |
Test reports are appreciated ;) (please report either success or failure to |
| 8 |
that bug). |
| 9 |
|
| 10 |
As for the negative version count, well it is now at 1.0 after being renamed |
| 11 |
and we can only hope that package developers will follow sane versioning. If |
| 12 |
not, we'll have to contact them and try to persuade to come to their senses |
| 13 |
:), or invent more elaborative name mangling scheme.. |
| 14 |
|
| 15 |
George |
| 16 |
|
| 17 |
|
| 18 |
On Friday 22 November 2002 01:37, Per Wigren wrote: |
| 19 |
> Hi! |
| 20 |
> |
| 21 |
> I'm about to make an ebuild of Sma{ll,rt}Eiffel and a new category |
| 22 |
> dev-eiffel with a lot of extra libs, modules, bindings etc.. |
| 23 |
> |
| 24 |
> The problem is that SmallEiffel is about to be renamed to SmartEiffel.. The |
| 25 |
> current stable release is SmallEiffel v0.74, but it will be soon be renamed |
| 26 |
> to SmartEiffel when it becomes v1.0 (it's currently 1.0beta5).. |
| 27 |
> |
| 28 |
> How to resolve this? If I make an ebuild for SmallEiffel v0.74 now, I want |
| 29 |
> it to be upgraded to SmartEiffel v1.0 when it is released.. It's the very |
| 30 |
> same compiler, just renamed.. |
| 31 |
> |
| 32 |
> Another problem is that the filenames doesn't contain the version-number... |
| 33 |
> All versions are named se.tgz so this will cause a problem when upgrading |
| 34 |
> if the old one is still in distfiles... |
| 35 |
> |
| 36 |
> Regards, |
| 37 |
> Per Wigren |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives