example of buildsys rpm

[Clark Williams]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

seth vidal wrote:
>> 1. okay - as panu was so kind to point out - we don't need 3 packages,
>> really. - just one
>> 2. I made the changes in mock cvs to have it install via a package of
>> the above style - the config option is chroot_dep_package
>> 3. what other patches need to go into mock before we release 0.5?
>>   - the one's I know about but wouldn't mind a reference to are:
>>     a. /dev/std* patch
>
>         1. the patch submitted to fix this is definitely in mock cvs
>         2. it is not entirely clear if this patch fixes the problem.
>
Well, it fixed it for me, but I wasn't the one that reported the problem.

> 1. Clark: could you modify your buildsys rpm so that it produces a
> single package named buildsys-build and could you check that spec file
> into mock cvs, since it will be handy there?
Sure.

In my original specfile I was playing kinda fast-n-loose, so I'd like
to insure that the values we use for Version and Release make some
sense. Should the Version field match our proposed mock version (i.e.
0.5)? Do we want to include the FC release in the release field (e.g.
fc5-1) or something like that? Or should Release just be a number
relative to the version string?


Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFEO8aUHyuj/+TTEp0RAghsAJ9RhsSQN2DU7tDNOHAVEL+I376MLACgu3SI
jwt3MGKrZb6lzvJuzcbWnaM=
=UNGV
-----END PGP SIGNATURE-----