[stgt] Facilitate building RPM packages

[FUJITA Tomonori]

On Fri, 11 Sep 2009 08:10:37 +0200
Florian Haas <florian.haas at linbit.com> wrote:

> 
> On 2009-09-11 01:36, FUJITA Tomonori wrote:
> > On Tue,  8 Sep 2009 11:18:56 +0200
> > Florian Haas <florian.haas at linbit.com> wrote:
> > 
> >> Hello everyone,
> >>
> >> here's a small set of patches to facilitate building tgt RPM
> >> packages. Largely inspired by the spec file created by Mike Christie
> >> for the scsi-target-utils package in RHEL. The sysconfig file and tgtd
> >> init script are unchanged from RHEL. Mike, hope that's OK with you.
> >>
> >> Overall diffstat:
> >>
> >> conf/sysconfig.tgtd |    2 +
> >> conf/targets.conf   |    2 +
> >> scripts/tgtd.init   |  150 +++++++++++++++++++++++++++++++++++++++++++++++++++
> >> tgt.spec            |  113 ++++++++++++++++++++++++++++++++++++++
> >> usr/Makefile        |    2 +-
> >>
> >> 5 files changed, 268 insertions(+), 1 deletions(-)
> > 
> > I think that distributions people don't want their package files in a
> > mainline (IIRC, a debian developer said it). As I correctly
> > understand, it's much easier for them to update their package files
> > freely without bothering maintainers.
> 
> Yes, Debian does have this policy. I don't think it applies to RHEL or
> CentOS though; besides if package maintainers want, they can always
> replace the spec with their own. Mike -- your thoughts?
> 
> I just find it complicated to have to manually merge the spec from RHEL
> with my own local git checkout, just to build reasonably up to date tgt
> packages.

You can easily maintain your own RPM files, pull the latest tgt code
occasionally, and sync them. Git works very well in such
situation. All you need to do is having a branch for your own RPM
files.
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html