NWN 1.68 Released, I just renamed nwn 1.67-r1 to 1.68 and it emerged just fine
Reading some forums, perhaps adding a USE flag to move override to override_bak would be nice, same as the installer on windows since people are getting weird issues with overrides
(In reply to comment #1)
> Reading some forums, perhaps adding a USE flag to move override to override_bak
> would be nice, same as the installer on windows since people are getting weird
> issues with overrides
We shouldn't do that in the ebuild. The override directory may contain files that do not belong to this package, among other reasons.
Exactly why we should do it, I had an override baseitems.2da and it messed up all kinda stuff for me
Just don't get your hopes up. It doesn't seem like the kind of thing that Mr. Gianelloni will be likely to commit.
Where did the rogue 2da file come from? It doesn't really seem like portage's responsibility to deal with files that it has nothing to do with.
I think it might be good just as a "clean" option or something. The rogue 2da came from an override for a server I play. The win32 installer caters for it but I understand if Mr Wolf won't :P
I've added this to CVS... and no, I'm not making provisions for anything not managed by portage... for one, it violates policy... but also, there's a certain level of "don't break your own shizzy" that's assumed... :P
Hello, I have emerge -av nwn and it installed the german version. Now I do speak german, but obviously i wanted the english version.
My linguas was set as: LINGUAS="en nl de" with en as main language.
Yet emerging nwn installed the german version. Somewhere a bug in the ebuild? Valid for a new bugreport?
Well, this bug was for a version bump, so it doesn't belong here, at all.
Anyway, that's the expected bahavior. If you have any languages defined, the ebuild uses them. I'm currently re-working the ebuild to use a different method, but if you were to file a bug on this, I'd likely resolve is as INVALID since the ebuild is doing exactly what it is supposed to do.