Re: [MinGW-dvlpr] Package Identification HOWTO [was: New packages]

[Keith M. <kei...@us...>]

On Tuesday 14 July 2009 01:47:51 Charles Wilson wrote:
> > 3) I haven't currently built as a shared library.  Obviously it
> > is fairly trivial to do so, in which case I will most likely
> > adopt the naming convention `libbz2-1.0.5-mingw32-dll-0.tar.gz'
>
> Sure, with two caveats:
>
> 1) I think the DLLVER is "1". At least, my linux box has
> libbz2.la: # Version information for libbz2.
>      current=1
>      age=0
>      revision=0
> so, C-A == 1.

But, by what authority does your Linux box assert that current = 1?  
The upstream bzip2 project doesn't use libtool, (nor indeed *any* of 
the autotool suite; remember, *I* undertook the autoconfiscation for 
my own benefit).  libbz2.la implies a libtoolization, which doesn't 
apply for *our* package, because I didn't, (and I don't intend to), 
libtoolize it.

This is the *first* *ever* build of bzip2, explicitly for mingw32.  
By the rules in the page you linked[*] to the HOWTO, that means that 
all of current, revision and age should be zero.  In any case, I am 
certainly not prepared to promise compatibility, to the extent of 
interchangeability, with anyone else's build, (over which we have no 
control); surely, what matters here is that we maintain consistent 
evolution of DLLVER numbering for *our* releases, irrespective of 
what others may do.

[*] I have a minor issue with the destination of that link.  Had it 
been to a page on cygwin.com, I probably wouldn't have given it a 
second thought, but it is to some user's personal home directory, on 
a host in an unrelated domain.  I have grave doubts concerning it's 
guaranteed longevity; (to say nothing of its inaccessibility from my 
office, where naive URL filtering seems to block any address which 
includes a tilde).  Perhaps we should seek permission to host a copy 
of the page, in our own style, on our own site.

> 2) if you add a build serial number to the other packages, you
> should also add one to the dll package.

Of course.

-- 

Regards,
Keith.