Here are a few more suggestions based on the OSX Fink package manager, which seem simple enough to just add here rather than create another Bugzilla entry.
Sometimes a source or patch file has an available URL, but the filename is not sufficiently unique. So I propose the following additional tags, each defining a file download URL:
Source[N]-URL:
Patch[N]-URL:
Icon-URL:
These would allow a different local filename, and could be used to prefix source and patch files with the main package name. It also allows for a download that uses an HTTP GET, where the standard %u2p macro will not work.
Fink also has a "Recommends:" tag. It allows a package to define software that it supports, but is not required.
Fink macros allow for access to subpackage names. An uppercase macro maps to the subpackage, and a lowercase macro always maps to the main package. The equivalent for SPEC files would be:
%{name} == the main package name.
%{NAME} == the subpackage name; same as %{name} in the main package sections.
Here are a few more suggestions based on the OSX Fink package manager, which seem simple enough to just add here rather than create another Bugzilla entry.
Sometimes a source or patch file has an available URL, but the filename is not sufficiently unique. So I propose the following additional tags, each defining a file download URL:
Source[N]-URL:
Patch[N]-URL:
Icon-URL:
These would allow a different local filename, and could be used to prefix source and patch files with the main package name. It also allows for a download that uses an HTTP GET, where the standard %u2p macro will not work.
Fink also has a "Recommends:" tag. It allows a package to define software that it supports, but is not required.
Fink macros allow for access to subpackage names. An uppercase macro maps to the subpackage, and a lowercase macro always maps to the main package. The equivalent for SPEC files would be:
%{name} == the main package name.
%{NAME} == the subpackage name; same as %{name} in the main package sections.