Axel.Thimm at ATrpms
Oct 22, 2009, 7:59 PM
Post #2 of 5
(741 views)
Permalink
|
On Thu, Oct 22, 2009 at 08:10:56AM -0700, Mark Goldberg wrote:
> Forgive me if this is described somewhere, but I could not find it, at
> least not in recent posts.
>
> I'm building my own myth rpms from the source rpm, adding a few
> patches. I know it may be the long way around, but it is convenient
> for me to do this and build sets of rpms to try things that can be
> easily swapped and help me with dependencies. I'm not a big fan of
> typing lots of commands and "make install" and "make uninstall" for
> such a big app. I like managing things with rpmbuild and modifying
> the spec file so I can duplicate things.
>
> I'm sure others will disagree with me, but, assuming this is what I
> am doing, where do the two tarballs in the source rpm come from? Do
> you have a script to check out a particular version from SVN and
> make the two tarballs?
I for one do not disagree, it's a fine way of developing, building,
testing and deploying patches.
The tarballs are created by emulating the release process, e.g. the
names of the tarballs, names of the folders within etc. look like the
structure that the released version will look like. That way I will
just swap out the self-made-tarballs-from-svn-trunk with the real
thing and the specfile changes will be just a Release: & %changelog
line change. There is no particular version, just the latest trunk.
--
Axel.Thimm at ATrpms.net
|
