Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Can we Have a release version #255

Open
shafeequ opened this issue Jul 1, 2020 · 6 comments
Open

Can we Have a release version #255

shafeequ opened this issue Jul 1, 2020 · 6 comments

Comments

@shafeequ
Copy link

shafeequ commented Jul 1, 2020

Team,

Since the popularity and usage of this are increasing, are you planning to have a Release version so that the consumer of this utility can use it?

Thanks,
@emil-e
Copy link
Owner

emil-e commented Jul 1, 2020

I don't really have any such plans given that I don't really have time to work on RapidCheck these days.

@shafeequ
Copy link
Author

shafeequ commented Jul 1, 2020

Thanks for the quick response, Just a thought with the current master state we can have one release tag ?

@ezzieyguywuf
Copy link
Contributor

I don't really have any such plans given that I don't really have time to work on RapidCheck these days.

Is this still the case? If so, are you interested in adding other people as maintainers to the project?

@emil-e
Copy link
Owner

emil-e commented Jul 2, 2021

I don't really have any such plans given that I don't really have time to work on RapidCheck these days.

Is this still the case? If so, are you interested in adding other people as maintainers to the project?

I would be very much open to that if I find someone appropriate, yes. It'd be a shame for this project just to rot because I'm busy. Are you interested or know anyone else who is interested?

@ezzieyguywuf
Copy link
Contributor

I don't really have any such plans given that I don't really have time to work on RapidCheck these days.

Is this still the case? If so, are you interested in adding other people as maintainers to the project?

I would be very much open to that if I find someone appropriate, yes. It'd be a shame for this project just to rot because I'm busy. Are you interested or know anyone else who is interested?

I am definitely interested. I would love to work on getting an official release, as well as cleaning up some of the pull requests and issues.

@alerque
Copy link

alerque commented Mar 11, 2023

This library has become a build dependency for projects like nix, which does have stable releases in distro packages. Now distros (like Arch Linux which I package for) are forced with dealing with packaging a library with no upstream versioning just to build other versioned packages. A tag now and then would be very much appreciated.

algitbot pushed a commit to alpinelinux/aports that referenced this issue Jul 6, 2023
@nmeum
testing/nix: disable tests to avoid dependency on rapidcheck
2428614 
rapidcheck is really not in a shape rn where we really want to
package it. Hence, disable check() in Nix until rapidcheck upstream
tags releases, uses versioned sonames, and provides a pkg-config file.

See: emil-e/rapidcheck#255
@nmeum nmeum mentioned this issue Feb 4, 2024
Open
algitbot pushed a commit to alpinelinux/aports that referenced this issue Feb 5, 2024
@nmeum
testing/rapidcheck: new aport
428901d 
This package is needed for the Nix test suite, it's really annoying
to package as upstream doesn't tag releases and, therefore, also
doesn't set an soname for the shared library.

However, running the Nix test suite in Alpine is beneficial as it
discovers bugs in Nix (see NixOS/nix#9934).

See also: emil-e/rapidcheck#255
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@alerque @ezzieyguywuf @emil-e @shafeequ