Re: Bug #866601: RFS: segyio package is ready
> I have a couple of changes that I would like you to make (by committing directly
> in the git, no need to restart from scratch). Sorry for not having caught them
> on my first initial review:
I'll address these right away.
> Note that if you do not want to bother with all the complexities related to a
> shared library (in particular the ABI tracking), an alternative is to make it
> a private library of the seygio-bin package (BTW, shouldn’t this package
> simply be called segyio?). But of course, if you do that, it will not be
> possible for other packages to depend on libsegyio.
I want to maintain it shared, because there some plans in our pipeline to make
more things depend on it. Hopefully we can deal with the pain.
The applications in the segyio-bin package aren't really the goal of the project
(the library and python library is), they just happened to be quick to write and
useful for us. I have no strong opinions on the package being named segyio over
segyio-bin, but I'm happy to change it either way.
> And as a final remark, please don’t top-post :)
My apologies, it's the stupid (unchangeable?) default of the mail client. I'll keep it in mind
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorized use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you
Reply to: