-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ignacio Vazquez-Abrams wrote: | On Mon, 2008-05-19 at 09:40 +0800, Gregory Hosler wrote: |> Hi all, |> |> new packager here. |> |> Apologies in advance for any ignorant questions. | | The only ignorant questions are the ones unasked. | |> First question: What is the procedure when there are changes to the spec file ? | | cvs update ; $EDITOR foo.spec ; cvs commit | |> I am gathering that changes are done in devel first, and then after they build correctly, |> those changes/updates are then applied to the respective branch from {EL-4, EL-5, F-7, |> F-8, F-9}, one at a time. Is this correct ? | | It's best to keep newer releases with newer ENVRs, but there's no | requirement to wait until a build is complete in devel before applying | it to the stable Fedora releases. You can use the mockbuild target to | give a "quick" shakedown of your package under a specific branch.
ok, so if I understand properly...
cvs update
go to the devel, directory, update the spec file, then
cvs commit
(And to clarify, the above commit should be delayed until several steps below, where I have done a build on my system, yes?)
and then
make new-sources FILES="yournewtarball.tar.gz"
Q: Do I have the tarball in the current (devel, or whatever) directory, or do I just specify the path to it, and "it doesn't matter" ?
Q: does the above line push the new tarball into cvs ? or do i need a commit ?
and then (if I understand correctly):
make i386
will make an i386 package on my current i386 system yes ? Once I have a successful build
cvs commit make tag make build
(all above 3 lines from the devel directory).
I'm terribly paranoid about submitting a package that will break while building, even though I've built it many times in my own environment...
Devel builds goes where ? F-10 ? F-9 ? rawhide ?
Thanks, and best rgds,
- -Greg
- -- +---------------------------------------------------------------------+
Please also check the log file at "/dev/null" for additional information. (from /var/log/Xorg.setup.log)
| Greg Hosler ghosler@redhat.com | +---------------------------------------------------------------------+