Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gauret]

Hi.

I'm packaging aMule for fedora and I am running into something I understand as a bug.
When you first start aMule, and if you've used xMule before, aMule just does a "mv ~/.xMule ~/.aMule", without changing the preferences. As a result, the Incoming and Temp directories are still set to ~/.xMule/{Incoming,Temp}, which no longer exist.

The best solution I can think of would be to have aMule copy the user directory instead of moving it, and then change the all the preferences containing .xMule to .aMule.

This way, we could have aMule and xMule on the same machine, the user could test both of them, and of course choose aMule freely ;-)

Can someone tell me if this is possible ?

Thanks

Aurelien

[Xaignar]

I personally think that the move-original-folder behavior is totally asinine. It just causes trouble, with no apparrent benefits, and when I first tried aMule, didn't even work right (it failed to changed the path entries as well).
I cant come up with any reason for using .aMule instead .xMule instead, considering the benefits of being able to switch between the clients. If you break comparability, then move the folder, but warn the user first.

[Guest]

This bug is also discussed here : http://bugzilla.livna.org/show_bug.cgi?id=2
This is a bugzilla for packaging bugs and request.

Some people proposed better solutions to this problem, so you may want to have a look at the discussion there.

Aurelien