Re: [opensuse-packaging] Building a package based on an existing spec file

On Fri, May 4, 2012 at 6:08 PM, Marguerite Su wrote:

On Fri, May 4, 2012 at 10:00 PM, Robert Munteanu wrote:

...

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

Hi,

I think you should copy it out.

Good points, thanks. Robert

reasons:

1. if spec file is in the archive, other OBS packagers have trouble change the content of spec file in the web interface. and reviewers can't review your package, because they see no spec. indeed in that way only upstream maintainers can change the spec when they make the tarball. so no collaboration on OBS. then it's not "open" developed or has some barriers to do so under existing infrastructure.

2. the spec is for Red Hat, openSUSE may need to change something to meet our benchmark. like Group Tag( Fedora has less tags than we are), Copyright Header( @2012 SuSE something), Changelog( OBS uses .changes file not inner %changelog), %Clean( OBS does not need that), and some macros may not existed on openSUSE.

3. actually, nowadays, without a spec in package source area. the build certainly fails. sometimes you can use service to fetch spec from internet, but anyways at last you have to put it in that folder with tarball.

marguerite

-- 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