I wouldn't recomend that for several reasons:
1) Most gems will install with all sort of twisted permissions; This
needs various fixings during the package which might cover file system
permissions amongst other things;
2) Many times upstream gems have complitely idiotic hashbangs
(usually known around also as shebangs); sometimes this requires a few
fixes during packaging;
My recomendation is that you use the provided spec and do all the
necessary changes so that you provide a cool package.
2012/5/4 Robert Munteanu
Hi,
I want to package a ruby gem[1] which already has a spec file [2] in the source tree . Is there a way to let OBS know that the spec is inside the archive or should I manually copy the spec out of the source tree ?
Robert
[1]: https://github.com/openshift/os-client-tools [2]: https://github.com/openshift/os-client-tools/blob/master/express/client.spec
-- Sent from my (old) computer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-- Nelson Marques // I've stopped trying to understand sandwiches with a third piece of bread in the middle... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org