You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on updating a few packages in the Ruby cucumber stack in Fedora and I noticed the license file is missing from this library now, that wasn't the case with v14.
From what I understand the file should be present in the released gem as it's a copy of the software.
Not 100% sure how a proper fix should look like.
AFAICT, to build and then unpack/install the gem properly, the license has to be either on the same level with the .gemspec file in the Ruby gem or some level below. A file cannot be referenced a level up from gemspec, so doing something like s.files << "../LICENSE" is not going to work for unpacking the gem. Perhaps a Rakefile target that copies the LICENSE first and then builds the gem so that something like s.files << "./LICENSE" would then be OK.
The text was updated successfully, but these errors were encountered:
Ah. That would have been my fault. I deduplicated the licenses in #195 and in other repos as well. We probably have this problem in quite a few projects then.
I am working on updating a few packages in the Ruby cucumber stack in Fedora and I noticed the license file is missing from this library now, that wasn't the case with v14.
From what I understand the file should be present in the released gem as it's a copy of the software.
Not 100% sure how a proper fix should look like.
AFAICT, to build and then unpack/install the gem properly, the license has to be either on the same level with the
.gemspec
file in the Ruby gem or some level below. A file cannot be referenced a level up from gemspec, so doing something likes.files << "../LICENSE"
is not going to work for unpacking the gem. Perhaps a Rakefile target that copies the LICENSE first and then builds the gem so that something likes.files << "./LICENSE"
would then be OK.The text was updated successfully, but these errors were encountered: