Re: Files listed twice question

Firstly, thank you for your answer Valery.

I didn't think of including this in my previous mail, but your comments=20
tells me it's relevant: I'm using rpm version 4.4.2 on CentOS 5.2.

Did I mention I'm the epitome of laziness? I've read about using find to=20
auto generate the file list, but then I'd have to 1) make the script and=20
2) run it for every release prior to packaging. Whereas the individual=20
files are bound to change significantly between releases, the config=20
dirs are pretty much fixed, so a setup like the one I had in mind would=20
be a one-time deal which I could unscrupulously copy/paste for all=20
future releases, thus taking me a step closer towards doing absolutely=20
nothing in exchange for my salary, which is my ultimate goal in life.

I'm afraid I might not have understood what you meant by:

 >> It allows cross-check between installation files into build-root and=20
filelist

you mean there's those extra checks such as that if I list a file that=20
is missing in the build-root the build will fail, and if the opposite=20
happens I'll be warned that there are files I haven't listed in my=20
build-root?
If so, I can't see the benefit, since (as I understood it) I'd be=20
running the find script to list whatever files end up in my build root=20
anyway, so in effect, there'd be no difference to globbing regarding=20
what files I'm including. If possible, please clarify this a bit for me=20
in the very likely case that I'm missing something.

As I gathered from past discussions the good thing about listing files=20
explicitly was that you could easily compare spec files to find out what=20
changed between releases. Are there other advantages?

All that being said, my original questions still stand. Can the warnings=20
be ignored? Is there a better way of doing what I want without=20
explicitly listing files?

Thank you all.

Adri=E1n.

Valery Reznic escribi=F3:
>
> --- On Wed, 9/24/08, Adri=E1n M=E1rques <[email protected]> wrote:
>
>  =20
>> From: Adri=E1n M=E1rques <[email protected]>
>> Subject: Files listed twice question
>> To: [email protected]
>> Date: Wednesday, September 24, 2008, 9:28 PM
>> Hi there,
>>
>> I'm an absolute newbie trying to package an application
>> with RPM for the=20
>> first time and would like to mark some files as config
>> files.
>> The top directory of this aplication has several files and
>> directories,=20
>> only two of which hold config files. Thus, I'm doing
>> something like this=20
>> in my spec file:
>>
>> %files
>> /usr/local/myAppTopDir/
>> %config /usr/local/myAppTopDir/configDir1/*
>> %config /usr/local/myAppTopDir/configDir2/*
>>
>> Obviously, this generates several 'file listed
>> twice' warnings. However,=20
>> I queried the generated rpm and didn't find anything
>> wrong with it. All=20
>> config files where included and correctly marked as config
>> files.
>>
>> So my questions are: can I safely ignore these warnings or
>> listing files=20
>> twice like I have causes a problem I'm not seeing now?
>> is there a better=20
>> way to do what I want?
>>
>> I have been looking through the list archives so I know
>> many of you=20
>> would advice me to explicitly list all files. I know this
>> would take=20
>> care of this particular problem, but I don't want to do
>> that unless I=20
>> really have to, since I find globbing significantly more
>> practical in=20
>> this case.
>>    =20
> It's strange that it's only warning at least before it was error.
>
> I personally prefer am list file explicit. It'sallows cross-check betwe=
en installation files into build-root and filelist.
> If you haven't too much files I suggest explicitly list them. If you ha=
ve too much you can use find to generate filelist on the fly.
>
> Valery
>  =20
>> I thank you already for taking the time to read this.
>>
>> Regards.
>>
>> Adri=E1n.