Matthias Klose writes:
> reopen 339237
> thanks
>
> > Changes:
> > openalpp-cvs (20060217-1) unstable; urgency=low
> > .
> > * upstream sync (closes: #339237)
>
> that's pretty much not a fix. even no reply on Steve's question in the
> bug report. please comment.
I overlooked the question. Sorry about that and thanks for the
reminder.
Regarding the name, openalpp-cvs reflects the fact that the
upstream do not do formal releases. However, the software has had a stable
API during the past two years. My hunch is that it's not likely to change
in the near future (library issued from research, fullfilling the needs
and not evolving much).
It would probably be appropriate to suffix it with 0 and do an
independent library versioning to avoid ABI problems.
I'd be tempted to leave the name as it is. The binary was
recompiled on the latest unstable and since the upstream version
changed I understood it was not necessary to prepend the c2a. Was I wrong ?
Thanks for your help,
--
Loic Dachary, 12 bd Magenta, 75010 Paris. Tel: 33 8 71 18 43 38
http://www.fsffrance.org/ http://www.dachary.org/loic/gpg.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
