aMule Forum

English => en_Bugs => Topic started by: Guest on November 22, 2003, 04:17:49 PM

Title: .xMule got deleted
Post by: Guest on November 22, 2003, 04:17:49 PM

Hello I just installed the SuSE/RH/MDK rpm for aMule 1.1.2 in SuSE 8.2.
When I first ran amule I got an error saying it couldn't find .xMule/Incoming and .xMule/Temp. I checked it and they were deleted!!!

That was really really bad!!
Is this a know bug? feature? rpm problem?

Thanks,

J.A.

Title: Opsss! Sorry, everything ok!
Post by: Guest on November 22, 2003, 04:29:11 PM

I got confused because of the error message.
It simply moved .xMule to .aMule after all but kept the old incoming and temporary files configurating.

J.A.

Title: Re: .xMule got deleted
Post by: gauret on November 26, 2003, 11:52:22 AM

Apparently, several people are complaining about this method.
We are trying to find the best solution to keep compatibility between aMule and xMule. You, or an aMule developper, may want to have a look here :
http://amule.sourceforge.net/phpBB2/viewtopic.php?t=184
and here :
http://bugzilla.livna.org/show_bug.cgi?id=2

Thanks

Aurelien

Title: Re: .xMule got deleted
Post by: Kry on November 27, 2003, 07:00:03 AM

Ok. People complaining about it have met their goal:


1) 1.2.0 does not remove .xMule, just copy config and credist files
2) it also gives a warning on import of directory to avoid user deleting .xMule if Incoming/emp are still there.

Hope that works.

Title: Re: .xMule got deleted
Post by: Guest on November 27, 2003, 10:40:46 AM

Quote

Original von Kry

Ok. People complaining about it have met their goal:


1) 1.2.0 does not remove .xMule, just copy config and credist files
2) it also gives a warning on import of directory to avoid user deleting .xMule if Incoming/emp are still there.

Hope that works.

Yes !

From a packaging point of view, this is *much* better. It's a very important step towards having aMule and xMule coexist on the same system.

The next step (if you are ok to take it... ;-) ) would be to rename aMule's ed2k to ed2k-amule and xMule's ed2k to ed2k-xmule, and then provide a symlink ed2k -> ed2k-amule for compatibility. Then, the package can update the symlink using the "alternatives" system, to choose between aMule and xMule. I think that our aMule and xMule packages for Fedora will use this trick, but it would be even better if the program was renamed upstream.

Thanks a lot for this great program and the work you've done.

Aurelien