If I'm not mistaken, the included libisofs in tdelibs is libisfs-0.2 from 2002.
One can note that the author has released libisofs-0.4 in 2007.
First, might nice to upgrade that library, then as suggested by @SlavekB we could make a standalone libisofs library since this code has already been duplicated in k3b and krusader.
If I'm not mistaken, the included libisofs in tdelibs is libisfs-0.2 from 2002.
One can note that the author has released libisofs-0.4 in 2007.
First, might nice to upgrade that library, then as suggested by @SlavekB we could make a standalone libisofs library since this code has already been duplicated in k3b and krusader.
https://sourceforge.net/projects/libcdrom/files/libisofs/
To be continued...
Without looked any deeper into that, I just looked in Gentoo for that and it's still in the tree and it seems it's just maintained now by the libburnia project too.
Good point, Greg. :+1:
Without looked any deeper into that, I just looked in Gentoo for that and it's still in the tree and it seems it's just maintained now by the libburnia project too.
* https://dev.lovelyhq.com/libburnia/web/-/wikis/home
Seems Gentoo is using that as libisofs now too.
Actually, at first, I though we could make It a shared library within tdelibs, because that code(lib) could be shared with k3b and krusader, then Slavek suggested a standalone lib.
I don't know what is the best solution here but switching to libisofs from libburnia sure is appealing.
I haven't had a look into the details but It's fair to assume that by the time a lot have changed (api) and switching tdelibs, k3b as well as krusader will require a bit of/some of/a lot of work.
Actually, at first, I though we could make It a shared library within tdelibs, because that code(lib) could be shared with k3b and krusader, then Slavek suggested a standalone lib.
I don't know what is the best solution here but switching to libisofs from libburnia sure is appealing.
I haven't had a look into the details but It's fair to assume that by the time a lot have changed (api) and switching tdelibs, k3b as well as krusader will require a bit of/some of/a lot of work.
The question here is whether to make efforts for existing libisofs or to leave it in its current state and pay attention to research on the possibility of using libisofs from libburnia.
The question here is whether to make efforts for existing libisofs or to leave it in its current state and pay attention to research on the possibility of using libisofs from libburnia.
As I know (Without looking deeper into that too) the libburnia developers wanted to offer their libs as drop-in replacement. At least that was the case for cdrecord. So maybe the API is still the same, more or less. But could be different, yes. Using shared libs sounds like some good option.
The same is for libparanoia. You can as far as I know use three different versions of it. Libburnia developers are keeping care of that lib too. But it seems there are quality differences. Therefore in Gentoo it is handled the way just to depend on one version to have installed of them. Maybe that would be good for TDE too. Just like done with OpenSSL and LibreSSL.
Isn't the original libisofs in the known distribution repos anymore?
As I know (Without looking deeper into that too) the libburnia developers wanted to offer their libs as drop-in replacement. At least that was the case for cdrecord. So maybe the API is still the same, more or less. But could be different, yes. Using shared libs sounds like some good option.
The same is for libparanoia. You can as far as I know use three different versions of it. Libburnia developers are keeping care of that lib too. But it seems there are quality differences. Therefore in Gentoo it is handled the way just to depend on one version to have installed of them. Maybe that would be good for TDE too. Just like done with OpenSSL and LibreSSL.
Isn't the original libisofs in the known distribution repos anymore?
I'm closing this issue because there is actually no need to upgrade libisofs-0.2 to 0.4.
The differences are aesthetics, "prettier" names for some functions (but their definitions is same code) and some pointers.
The author extracted the main function (which is not built by default) from the lib to make a standalone prog.
In short no new features, no fixes that we could care about.
Making a standalone libisofs library that links with tdelibs, k3b and krusader is an other matter.
I'm closing this issue because there is actually no need to upgrade libisofs-0.2 to 0.4.
The differences are aesthetics, "prettier" names for some functions (but their definitions is same code) and some pointers.
The author extracted the main function (which is not built by default) from the lib to make a standalone prog.
In short no new features, no fixes that we could care about.
Making a standalone libisofs library that links with tdelibs, k3b and krusader is an other matter.
If I'm not mistaken, the included libisofs in tdelibs is libisfs-0.2 from 2002.
One can note that the author has released libisofs-0.4 in 2007.
First, might nice to upgrade that library, then as suggested by @SlavekB we could make a standalone libisofs library since this code has already been duplicated in k3b and krusader.
https://sourceforge.net/projects/libcdrom/files/libisofs/
To be continued...
Good point, Greg. 👍
Without looked any deeper into that, I just looked in Gentoo for that and it's still in the tree and it seems it's just maintained now by the libburnia project too.
Seems Gentoo is using that as libisofs now too.
Actually, at first, I though we could make It a shared library within tdelibs, because that code(lib) could be shared with k3b and krusader, then Slavek suggested a standalone lib.
I don't know what is the best solution here but switching to libisofs from libburnia sure is appealing.
I haven't had a look into the details but It's fair to assume that by the time a lot have changed (api) and switching tdelibs, k3b as well as krusader will require a bit of/some of/a lot of work.
The question here is whether to make efforts for existing libisofs or to leave it in its current state and pay attention to research on the possibility of using libisofs from libburnia.
As I know (Without looking deeper into that too) the libburnia developers wanted to offer their libs as drop-in replacement. At least that was the case for cdrecord. So maybe the API is still the same, more or less. But could be different, yes. Using shared libs sounds like some good option.
The same is for libparanoia. You can as far as I know use three different versions of it. Libburnia developers are keeping care of that lib too. But it seems there are quality differences. Therefore in Gentoo it is handled the way just to depend on one version to have installed of them. Maybe that would be good for TDE too. Just like done with OpenSSL and LibreSSL.
Isn't the original libisofs in the known distribution repos anymore?
I'm closing this issue because there is actually no need to upgrade libisofs-0.2 to 0.4.
The differences are aesthetics, "prettier" names for some functions (but their definitions is same code) and some pointers.
The author extracted the main function (which is not built by default) from the lib to make a standalone prog.
In short no new features, no fixes that we could care about.
Making a standalone libisofs library that links with tdelibs, k3b and krusader is an other matter.
ok, no problem.