Currently there are multiple spec file repositories (apart from jds):
spec-files-other, sfe, belenix.
The convention used across these are by & large the same except for
one notable difference - the package prefix
spec-files-other uses SUNW. Ex: gcc package would be SUNWgcc.pkg
sfe repo uses SFE. Ex: gcc package would be SFEgcc.pkg
belenix currently uses SFE but will move to "no prefix" based
package names. Ex: gcc package would be gcc.pkg
Some of us working on the belenix repo also work on sfe repo. As and
when we create new specs in belenix repo, we would like to put them
into sfe as well with minimal effort.
Similar is a situation when people want to move specs from SFE to
spec-files-other.
To make the movement of the spec files easy between the repos, here is
a proposal based on a discussion I had with laca on the #pkgbuild IRC.
The proposal to make this possible is to introduce a pkg_prefix macro
into one of the suitable include files. The package names will be
addressed using the macro instead of hard-coding the names.
This should cover package name as well as dependency information. This
would be a one time work and may be done as and when a spec is taken
up for editing.
Thoughts welcome.
regards
Shiv
