[Bug 211623] Review Request: libtcd - Tide Constituent Database Library

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: libtcd - Tide Constituent Database Library


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211623





------- Additional Comments From mtasaka at ioa.s.u-tokyo.ac.jp  2006-10-20 19:02 EST -------
(In reply to comment #2)
> Several issues:
> 
> * First of all, I don't think this split-off is convenient. It increases
> maintenance requirements with questionable benefit:
> 
>  - upstream do not ship libtcd in a separate tarball
>  - you include the xtide tarball in two src.rpms
>  - you introduce an own SONAME and ABI
>  - you can update xtide without building an included newer libtcd
> 
> As long as upstream doesn't treat libtcd as a separate release, why
> don't you build packages "libtcd", "libtcd-devel" and "tcd-utils"
> from inside the xtide src.rpm instead?
> 
> What other programs want libtcd?
libtcd is also required by harmbase2 (I don't know well this package and
I have not yet made srpm for this) in 
http://www.flaterco.com/xtide/libtcd.html. 

In this html, upstream considers the case that people want to seperate libtcd.
And upstreams of libtcd and xtide are different......

I don't think that including tcd-utils and xtide in same srpm is
proper because I have to recompile both even if I want to apply a 
patch for one of the packages and have to bump release.

> 
> 
> * Versioning:
> 
> > +SOMAJOR = 21
> > +SOMINOR = 0
> > +SOVER   = 3
> 
> Upstream uses MAJOR_REV 2 and MINOR_REV 1. Where does your versioning
> scheme originate? As long as upstream uses only static libs, do you want
> to increase major/minor/release appropriately?

Having MAJOR 2 and MINOR 1 means "libtcd.2.0 and libtcd.2.1 are API
compatible. However, as far as I read libtcd.html, it is NOT!!

Anyway, before fixing packaging xtide related packages, we must
decide if we should split libtcd (I think should).  This issue
affect the whole scheme of packaging xtide.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.