• entries
53
56
• views
33818

267 views

Nothing major, I just want to get a reaction from a few people here.

One of the abilities in an Installer Image is that of breaking the files to be installed into Components. This is pretty much as it suggests, a collection of related files that the user has a choice of installing or ignoring.

However, when I was designing my structures first, I put each component inside a single BaseDirectory, that being the folder that the component is installed into. Each file is installed to a path relative to the base directory.

However, it has struck me that perhaps I should restructure this the other way around, make the Component the top level structure, and put the directories inside that.

What do you guys think?

Each component should be totally path-agnostic; I should be able to put a file into an arbitrary path (absolute, relative, or relative to some variable like %system32%) from any component. Components should be only about grouping installed files, not about imposing file structure.

For instance:
MAIN STUFF
%appinstall%/engine.exe
%appinstall%/data/graphics.dat
%appinstall%/data/sounds.dat
%system32%/graphicslibrary.dll

REALLY KICKASS AUDIO COMPONENT
%appinstall%/extrasound.dll
%appinstall%/data/moresounds.dat
%system32%/soundlibrary.dll

I guess that makes a bit more sense alright.

This would be more along the lines of what I was thinking of, except where I have elements that represent the folders, you just leave them in the files path. I had move them up a level to allow for the possibility of applying attributes to the folder at a later date with the minimum of difficulty.

Create an account

Register a new account