-
Notifications
You must be signed in to change notification settings - Fork 45
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.
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
Generating Source1 with comment lines #111
Comments
I am not against this idea. However, it should be somehow linked to heuristics that the test suite is actually excluded. Also, bonus points for checking that there is actually some test suite available upstream. But on this place, I should also note that gem2rpm should not become slow due to extensive heuristics and checks. BTW, thinking more about this, gem2rpm could even generate the tarball, right? ;) |
The auto generation is also great. ^^ |
What a fun idea! Although it is generic problem, so it might be better to call other tool; and not duplicate the implementation
|
I do intend to (at least) create a template + probably some gem2rpm library addition to generate all this. Let me know if you're interested to collaborate. |
Grooming the backlog a bit, it turns out this is duplicate of #102, therefore I am closing this ticket. |
I think the following tips, and the lines to create an archive file for test files is great that is used on this PR https://src.fedoraproject.org/rpms/rubygem-pg/pull-request/9 . And I want to see the lines are auto-generated by
gem2rpm
for more people to know the tips.I want to see the following kind of lines are generated by
gem2rpm
. In my rough idea, the lines can be added like this totemplates/fedora-27-rawhide.spec.erb
by given<repository_url>
.The steps might be
gem2rpm <gem file>
.gem2rpm
get metadata from the given gemspec (e.g. pg.gemspec) orGem
lib.spec.metadata["source_code_uri"]
asrepository_url
.repository_dir_name
fromrepository_url
.test_dir_name
(=test
orspec
) from*.gemspec
spec.files
.fedora-27-rawhide.spec.erb
.The text was updated successfully, but these errors were encountered: