rpms/foremost/devel foremost.spec,1.2,1.3

[Toshio Ernie Kuratomi (toshio)]

Author: toshio

Update of /cvs/extras/rpms/foremost/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20515

Modified Files:
	foremost.spec 
Log Message:
* Mon Feb 13 2006 Toshio Kuratomi <toshio at tiki-lounge.com> 1.1-1.1.20060128
- Note on upstream's "beta" system to keep future maintainers out of trouble.
- Rebuild for the FC5 push.



Index: foremost.spec
===================================================================
RCS file: /cvs/extras/rpms/foremost/devel/foremost.spec,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- foremost.spec	29 Jan 2006 04:23:56 -0000	1.2
+++ foremost.spec	13 Feb 2006 18:24:48 -0000	1.3
@@ -1,15 +1,30 @@
 Name:           foremost
 Version:        1.1
-Release:        1%{?dist}
+# Note: This is a prerelease snapshot because upstream's release management
+# fooled me.  Move to a pre-release style tag modified for the initial
+# confusion.  Please see the Pre-Release section of:
+# http://www.fedoraproject.org/wiki/Packaging/NamingGuidelines
+# to figure out how to increment this for packaging changes.
+Release:        1.1.20060128%{?dist}
 Summary:        Recover files by "carving" them from a raw disk
 
 Group:          Applications/File
 License:        GPL
 URL:            http://foremost.sf.net
-# Upstream wasn't versioning their tarballs.  Record of the latest md5sum in
-# case that happens again.
-# b606cc602f38f0e370531f5c7911addb  foremost-1.1.tar.gz
+# Upstream is releasing new tarballs on foremost.sf.net/pkg (linked from the
+# foremost.sf.net website.) that have normal "x.y" style version numbers _but_
+# are essentially betas.  These files get overwritten as new "betas" are pushed.
+# When the release goes final, it is released through the normal sourceforge
+# file release mechanism with the same x.y version number.
+#
+# For sanity, in the future, we'll stick with packages released through the
+# sourceforge file release channel.  Since we've already been suckered in for
+# this cycle, I've reviewed the changes against foremost-1.0 and decided that
+# it's better to stick with the beta we currently have than to bump epoch and
+# go back to the 1.0 release.  MD5Sum of our download in January:
+# b606cc602f38f0e370531f5c7911addb foremost-1.1.tar.gz
 Source0:        http://foremost.sourceforge.net/pkg/%{name}-%{version}.tar.gz
+# Source0:	http://dl.sf.net/%{name}/%{name}-%{version}.tar.gz
 Source1:       COPYING
 BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
 
@@ -53,6 +68,10 @@
 %config(noreplace) %{_sysconfdir}/foremost.conf
 
 %changelog
+* Mon Feb 13 2006 Toshio Kuratomi <toshio at tiki-lounge.com> 1.1-1.1.20060128
+- Note on upstream's "beta" system to keep future maintainers out of trouble.
+- Rebuild for the FC5 push.
+  
 * Sat Jan 28 2006 Toshio Kuratomi <toshio at tiki-lounge.com> 1.1-1
 - Upgrade to 1.1.
 - Rework the config patch as a sed replacement.