how to include rpm-specific files in the spec

[Hubert Plociniczak]

Hello,

I couldn't find answer to my question on any guidelines page, so I am 
going to ask the question on the list.

The problem I have is that we have a rpm package (obviously) that uses 
some general tarball of the product as a source. Additionally we have 
rpm-specific files like .spec, init.d script, README, other scripts etc.
Now the question is how should we include them in the package.
I see two options:
1) include them as another source in the spec, so we will have two 
source tarballs
2) include rpm-specific files as a patch

Are there any others?
Now, under debian, the debian-specific files are included in diff.tar.gz 
so I was wondering if under rpm the recommended way is option 2.

Thanks for help.

Hubert

[Rex Dieter]

Hubert Plociniczak wrote:
> Hello,
>
> I couldn't find answer to my question on any guidelines page, so I am 
> going to ask the question on the list.
>
> The problem I have is that we have a rpm package (obviously) that uses 
> some general tarball of the product as a source. Additionally we have 
> rpm-specific files like .spec, init.d script, README, other scripts etc.
> Now the question is how should we include them in the package.
> I see two options:
> include them as another source in the spec, so we will have two
>
> source tarballs

option 1 is reasonable.

-- Rex

[Jarod Wilson]

On Friday 10 October 2008 08:49:59 Hubert Plociniczak wrote:
> Hello,
>
> I couldn't find answer to my question on any guidelines page, so I am
> going to ask the question on the list.
>
> The problem I have is that we have a rpm package (obviously) that uses
> some general tarball of the product as a source. Additionally we have
> rpm-specific files like .spec, init.d script, README, other scripts etc.
> Now the question is how should we include them in the package.
> I see two options:
> include them as another source in the spec, so we will have two
>
> source tarballs
> 2) include rpm-specific files as a patch
>
> Are there any others?
> Now, under debian, the debian-specific files are included in diff.tar.gz
> so I was wondering if under rpm the recommended way is option 2.

Either 1 or 2 is acceptable, or even a mix of the two. Note that for #1, they 
don't necessarily have to be tarballs, the can be individual files if it makes 
sense. Pretty much up to the packager's best judgment how to get the 
additional bits included, the most important part is that the primary 
tarball(s) are pristine upstream sources (barring any license or patent issues 
that require ripping something out).

[Hubert Plociniczak]

Hubert Plociniczak wrote:
> Additionally we have 
> rpm-specific files like .spec, init.d script, README, other scripts etc.

My mistake, spec file doesn't belong to this group of files.

One other, most commonly option is to just include tarball with already included rpm specific file. But then the source tarball would be different from the one that is publicly available...

Hopefully someone will clarify this to me.

Thanks,

hubert

[Jarod Wilson]

On Friday 10 October 2008 09:21:48 Hubert Plociniczak wrote:
> Hubert Plociniczak wrote:
> > Additionally we have
> > rpm-specific files like .spec, init.d script, README, other scripts etc.
>
> My mistake, spec file doesn't belong to this group of files.
>
> One other, most commonly option is to just include tarball with already
> included rpm specific file. But then the source tarball would be different
> from the one that is publicly available...

That's definitely a no-no.