Project status/plans for official release?

[rupran]

Hi everyone,

we are currently considering the use of librtpi in a part of our software stack and were wondering what the current status of the project is. Are there any issues left to solve? As the upstream glibc bug report is still open, I assume that glibc itself still has not fixed the issue or is planning to address it in the foreseeable future.

In the 2020 ELC talk, @gratian mentioned that there could be an "official" release when remaining issues are merged. Is this still something you consider doing? With an official release, it might also be easier to create packages of librtpi for various distributions as they can refer to a specific version instead of a commit hash. Do you have any plans for packaging the library yourself?

In any case, thanks for building this library already!

[gratian]

Hi @rupran,

@dvhart asked me to take over as maintainer at the end of last year. I've said yes but I have to admit I have not done much since. Part of the reason for the lack of action is I wasn't sure if anybody other than us (at NI) uses it or is interested in it. This made it harder to prioritize higher than my other day-to-day work. FWIW we at NI have been using a variant of librtpi in production for over 3 years now.

Now that I know there is at least one other person/group interested in it I have the motivation needed and I was able to get agreement today from my employer to spend some "work time" on it over the next few months. Hopefully I can give you more updates soon.

[fbezdeka]

Hi all,

instead of maintaining librtpi over the long run, has there been some movement on glibc side to fix this issue? Are there any references to ongoing discussions? Is there a "glibc can not fix it" statement somewhere?

I think most RT (real time) applications based on PREEMPT_RT are affected by this problem. Wouldn't it be nice to simply be able to use the infrastructure provided by glibc instead of using the librtpi APIs?

[gratian]

Hi @rupran, I've finally found some time over the last couple of weeks to migrate 'librtpi' to a better home at: https://gitlab.com/linux-rt/librtpi and integrate all my outstanding changes which fix the remaining test failures. I've also setup a backup repo at: https://github.com/linux-rt/librtpi

At this time all tests are passing on x86_64, and ARM (32-bit). Any additional testing would be appreciated. Patches are always welcome.

I've also bumped the version to 1.0.0 and tagged it as a release: https://gitlab.com/linux-rt/librtpi/-/releases

@dvhart, per our previous email discussion, we can update the README at this location to point to the new repo. Let me know if you want a PR.