Hi,
On Thu, Apr 12, 2007 at 09:59:54PM +0200, Till Maas wrote:
> | If a snapshot package is considered a "pre-release package", you should
> | follow the guidelines listed in Pre-Release Packages, and use an %{alphatag}
> | in the following format:
> | YYYYMMDDcvs
>
> Maybe this is useful for cvs, because there is no better way to describe a
> snapshot. But e.g. with svn, which uses a global revision number, it is
> possible to use a unique id for the snapshot, where it is not uncertain which
> changes are included.
Well, you are correct, just keep two things in mind:
a) the guideline above is a "should" guideline, which means no
enforcement. So any sensible scheme is OK with the guidelines.
b) The idea is to avoid packaging snapshots. Of course there are
projects that never release and still have a very good codebase
that is worth packaging. But instead of putting energy into how to
deal with unreleased software, maybe it's better to invest in
persuading or helping the upstream project to stamp off a release.
FWIW if you're going to package svn sheckout the more or less
canonical "snapshot" tag is r<snvrevison>, e.g. prepend a lower "r" in
front of the revision.
--
Axel.Thimm at ATrpms.net
Attachment:
pgpr32Jq27CtO.pgp
Description: PGP signature
-- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
