Re: Adding sha256 support into jigdo tools (jigdo and jigit)

2019-11-20 Thread Thomas Schmitt
Hi, Steve McIntyre wrote: > Let's go with "-jigdo-checksum-algorithm" to keep the separation? The user is king. Other mail: I proposed to keep versioning and SONAME at 1 > > LIBJTE1 { Steve McIntyre wrote: > Surely that works for upwards compatibility, but won't stop somebody > from building

Re: Adding sha256 support into jigdo tools (jigdo and jigit)

2019-11-20 Thread Steve McIntyre
On Wed, Nov 13, 2019 at 12:04:31AM +0100, Thomas Schmitt wrote: >Hi, > >SONAME comes from libjte/configure.ac. Dunno from where libburn got the >slightly braindamaged way to compose it. From there it spread over the >other libraries. libjte is its youngest victim. Shrug. Right. >The upstream

Re: Adding sha256 support into jigdo tools (jigdo and jigit)

2019-11-20 Thread Steve McIntyre
On Tue, Nov 12, 2019 at 11:37:29PM +0100, Thomas Schmitt wrote: >Hi, > >while exploring the need for adaptions in the build system of libsofs, >i wonder whether it is really necessary to create LIBJTE2 in libjte.ver. >Adding new functions is upward compatible. >In my libraries i add them to the

Re: Adding sha256 support into jigdo tools (jigdo and jigit)

2019-11-20 Thread Steve McIntyre
[ Arg, sorry to keep you waiting for responses. Really busy week... :-/ ] On Tue, Nov 12, 2019 at 10:10:04PM +0100, Thomas Schmitt wrote: >Hi, > >i wrote: >> > libjte_set_checksum_algorithm() became necessary > >Steve McIntyre wrote: >> ACK. I'd not thought that through fully myself here, but