<a class="font-weight-bold ml-2" href="/fork/vondruch/packaging-committee/blob/e28c92f8f7682196425f3ab7736826bf22fb573f/f/guidelines/modules/ROOT/pages/Ruby.adoc"
title="View file as of e28c92f">guidelines/modules/ROOT/pages/Ruby.adoc</a>
- Since gems aren't a standard archive format that rpm knows about and they encapsulate both an archive format and information to build the ruby library building an rpm from a gem looks a little different from other rpms.
+ Since gems aren't just archive format, but they encapsulate both an archive and information to build the ruby library, building an rpm from a gem looks a little different from other rpms.
A sample spec for building gems would look like this:
RPM can expand .gem and its metadata since RPM 4.14, so the information
in guidelines is missleading. This change tries to rectify the situation
a bit.
RPM can expand .gem and its metadata since RPM 4.14, so the information
in guidelines is missleading. This change tries to rectify the situation
a bit.