How should I build a data SIS file with a whole directory

[-chris-]

Hi all,

I've some problems building a SIS with data only included ("SISOPTION" type i guess). What I'd like to do is to install a complete directory with ca. 20 files. Is there a possibility to list the directory in the pkg or do I have to enter an entry for each and every file? As this is language dependant I'd have to enter more than 200 files manually if I can't include a directory

Thanks for your help!

Chris

[symbianyucca]

I think you gotta add them each separately.

[-chris-]

just feared exactly that ... thanks, yucca!

[-chris-]

hum - got another problem: I've got sort of language packs, each of which has files specific to the language and generic files. Now, if I install 2 language packs, I get "Update Error" because the 2nd language packs includes files already installed with the 1st and thus does not install them. How can I check for existence of a certain file and install only if it is not found?

[wizard_hu_]

You should forget that design. Though .pkg supports "if exists", it does not support "!:" in the condition, and it is hard to track what happens on uninstallation of the partial packages.
Eliminate overlapping files - if they are really localized ("xy.z01", etc.), they can not clash.

[-chris-]

actually I can't eliminate the overlap - I've got language pack german with german data libs + german option A + german option B. The user will have the choice to install either A or B or A+B. So there's no solution besides building three SIS files ("A" "B" "A+B")?

[-chris-]

maybe somehow building a SIS with generic german files and then somehow including this SIS in option A and option B?
Just a sidenote - do I have to pay for each and every SIS file someday when all this mess has to go to symbian signed?

[-chris-]

hmm i fixed this by installing both option A and B to different paths and each time including the general libs. Not a good choice from a space-saving perspective but best for user experience. Thanks for your help!