Dev Team,
I want to hear your thoughts about how we should structure the code
that creates installable packages for the various OS flavors. It
seems we need a separate build&pkg script for each OS, or one script
that can build any/all of them via subroutines, includes, or plug-ins.
It would be nice to strike some balance between chaotic individualism
and stifling circumscription.
Currently, SGI's needs are met via the Makepkgs script, which deposits
RPMs into the build subdirectory. Does it only do RPM's, or can it
also create Irix inst packages in some way that is not immediately
obvious to me?
The recent patches I sent in added a Macpkg script, vaguely similar
to Makepkgs, for creating MacOS packages. There is also a new subdir
of ancillary packaging/installer files. Additional OSs will require
similar additional infrastructure.
It seems silly to add another top-level script - and AixPkg or
HpPkg - for each additional OS. But, then, perhaps that is the most
straightforward solution.
I was thinking there might be some reasonable way to structure a single
top level script, that in turn executes platform specific build&pkg
code embedded in the subdir of ancillary installer files. However,
this begins touching on code pertinent to SGI's internal processes.
Alternately, the SGI code could remain as is; and the other OSs
could share some separate infrastructure.
What are your thoughts on this issue?
- mtw
|