Sourcecode mixing when updating [SOLVED]

[xenic]

Because I have a few programs located in non-standard locations on my system, I get offered updates I don't really need. I usually uncheck the things I know I don't need but yesterday I forgot and AmiUpdate downloaded Mixer and mpg123 library. When I checked my AmiUpdate download directory, I noticed that the Mixer sourcecode and mpg123 sourcecode were mixed together in the same directory. The reason I noticed the problem is because I copy all program sources to one location as example code that I can easily search. I forget who maintains the various update sites for AmiUpdate but I think there needs to be some standard for the update archives that avoids mixing of extracted directories. Each update should extract all it's contents to a single directory or common dirctory names like "src" need to be made more explicit like "Mixer_src" & mpg123_src. In a case like mixer/mpg123 it's possible that one makefile gets overwritten by another and only one of the programs can be compiled.

It's not a big problem for me because I noticed the problem but at some point somebody may be confused when they examine the mixed up sources.

[nbache]

Are you perhaps missing the checkmark for "Unpack updates into their own named sub-directories" on the last tab page of the Updates prefs?

Best regards,

Niels

[xenic]

Are you perhaps missing the checkmark for "Unpack updates into their own named sub-directories" on the last tab page of the Updates prefs?

Duh, yes that appears to be the solution. Thanks. I tried to test the solution and I can see that Mixer is now extracted to it's own directory. However, I couldn't get AmiUpdate to offer an update to mpg123 library even when I removed it from libs: and tried after a reboot. It is listed in the AmiUpdate log so I assume it's just a temporary server issue whereever the archive is located.

[nbache]

However, I couldn't get AmiUpdate to offer an update to mpg123 library even when I removed it from libs: and tried after a reboot. It is listed in the AmiUpdate log so I assume it's just a temporary server issue whereever the archive is located.

Some updates require a previous version to be installed already, for instance I can see in my own AU logs that it looks for that library in libs: and doesn't find it (correct; I don't have it and didn't even know its existance ). But it doesn't offer it for download for me either. I cannot see exactly how the server database entry was made, but you would probably get the offer if you had replaced an earlier version of the library in libs: instead of removing it altogether.

Best regards,

Niels

[Rigo]

The clue is in the name: AmiUpdate - therefore it UPDATES software. This in turn denotes that it has to actually find something installed in order to update it.

Simon