Am Sonntag, 13. Januar 2019, 08:56:34 CET schrieb Thorsten Kukuk:
On Sat, Jan 12, Eric Schirra wrote:
With other packages there are more lines which i must insert for such problem. And why should i put many lines with %dir when i can put only one line with BuildRequires?
Because the filelist is important for installing/de-installing the package, not for runtime. Assume your package BuildRequires apache2, but as it only requires a web server, not especially apache2, it would also work with nginx.
1. the directories would not be owned by any package hm. My dir under the rest from apache belongs to my package. And the rest to apache. Not right?
2. de-installation of the package would not remove the directory Think so. My dir under apache will be delete when i remove my package. Rest of apache will be there. Not right?
3. in worst case, RPM creates the directories with wrong permissions and your application will not work. hm. But what happend when i say 777 and other package say 666? Who is right? And who has the right?
As written, as long as your package does not require apache2, a BuildRequires for apache2 to fool the rpmlint scripts is plain wrong.
Hello Thorsten, I do not want to do anything different to do it differently. But I do not just want to do something just because one or the other says so. Or because it has always been done that way. I want to do it because I can agree, because the arguments were good and they convinced me. I think you german. Right? Can you please explain me all this in German per email? I don't want do Regards Eric -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org