[csw-maintainers] GAR Update: Copyright notices and dynamic gspec-files
Dagobert Michelsen
dam at opencsw.org
Fri Feb 6 23:31:17 CET 2009
Hi,
I have finished copyright notices and dynamic gspec-files in GAR.
To give you a quick start here are some facts:
Dynamic gspec-files are constructed as follows:
- Packages using dynamic gspec-files must be listed in PACKAGES
- There is a default of PACKAGES containing one packages named CSW
followed by the GARNAME. It can be changed by setting PACKAGES
explicitly.
- The name of the generated package is always the same as listed in
PACKAGES
- The catalog name defaults to the suffix following CSW of the package
name,
but can be customized by setting CATALOGNAME_<pkg> = <catalogname-
of-pkg>
- If only one package is build it is sufficient to set CATALOGNAME =
<catalogname-of-pkg>
It is an error to set CATALOGNAME if more than one package is build.
- If the package is suitable for all architectures (sparc and x86)
this can be
flagged with ARCHALL_<pkg> = 1 for a specific package or with
ARCHALL = 1
for all packages.
Dynamic licenses are selected in the following way:
- Dynamic licenses are only activated for packages listed in PACKAGES or
packages which don't have %copyright in their gspec-file. This way
the
behaviour on existing gspec-files is preserved.
- The default name for the license is COPYING and it will not be fully
printed
- If no license is explicitly specified in the Makefile and the
default can not
be found no license will be included
- If a license is specified it must be found or an error is issued
- Either LICENSE_<pkg> or LICENSE_FULL_<pkg> may be specified, it is
an error
to specify both.
- There is an automatic rule to include only the license for each
package that
belongs to it.
- Package-specific defines have precedence over general defines
(CATALOGNAME_<pkg>
before CATALOGNAME etc.)
There is also some draft documentation at
https://apps.sourceforge.net/mediawiki/gar/index.php?title=Copyright
https://apps.sourceforge.net/mediawiki/gar/index.php?title=Packaging
You can take a look at pca, autoconf, dtracetoolkit or libtool as
examples.
Please let me know if you encounter something unusual.
Best regards
-- Dago
More information about the maintainers
mailing list