Changes between Version 52 and Version 53 of RpmHowToPackagers

Timestamp:

Feb 3, 2017, 7:43:51 PM (7 years ago)

Author:

dmik

Comment:

--

RpmHowToPackagers

@@ -21 +21 @@
 If, for some reason, you fail to find the right .spec file in the Fedora repository (which is unlikely), you may try to search it in other places using the RPM find services like [http://rpm.pbone.net/ rpm.pbone.net] or [http://www.rpmfind.net www.rpmfind.net]. Enter the name of your package, and choose a distribution: prefer Fedora (see above) or OpenSUSE if Fedora is not available. Select your package from the left link, you will get a page with all details; one of them is the .src.rpm package, it contains the spec file, platform specific patches, package sources (in .tar.gz, .tar.bz2, .tar.xz format). Use  unrpm.cmd (check bootstrap directory) to extract all files to a temporary location.
 
-When you create an OS/2 .spec file based on the existing one, please always reference the original file the first line of the resulting .spec file, like this: [source:/spec/trunk/SPECS/nspr.spec#L1] (i.e. you put either an URL to the Fedora .spec file or to the SRPM file you used to get .spec from). This is important for further updating.
+When you create an OS/2 .spec file based on the existing one, please always reference the original file at the first line of the resulting .spec file. If you use the Fedora .spec file taken from the Git repository, please reference the commit number like in this this .spec file: [source:/spec/trunk/SPECS/libvpx.spec?rev=950#L1]. Otherwise please specify an URL of the source where you take the .spec file from. This way we will be able to keep our .spec files properly updated as the original .spec file gets updates to reflect new software versions.
 
 If you create a .spec file for new or proprietary software then you most likely don't have a .spec file to copy from. In this case it's best to select some similar application or library among existing OS/2 or Fedora .spec files and use it as a template.