Thanks for explaining that!
But now, all the RPM packages that I have this issue with are installing
correctly with RPM-4.x as that the directory structure are listed when
using -qlp, but with RPM-5.3.11, the package manager complain about the
directories until I use the --nodeps to workaround it, hence it installs
correctly and it does create the needed directories.
On Sun, 04 Sep 2011 16:47:38 +0200, Jeff Johnson <n3...@mac.com> wrote:
On Jun 4, 2010, at 2:55 AM, Belal Salem wrote:
Hi there!
I issued the same issue before, when installing some packages, the RPM
package manager doesn't create the required folders and ask for the
folders as unresolved dependencies, although those folders are part of
the package being installed.
Its "part of the package" which is confusing.
There are two meanings for "part of the package":
1) directory components as part of file paths
2) directory explicitly listed in "rpm -qpl *.rpm"
If its not explicitly in the file manifest, its not "part of the package"
and you *will* see what you are reporting.
Recompiling RPM with the options: --disable-dirname-and-symlink-deps
didn't solve the problem, anyway through that?!
I'm not the person to "fix" --disable-dirname-and-symlink-deps.
My fix will be to rip out the "Have it your own way!" functionality that
isn't "working"
and remove the
--disable-dirname-and-symlink-deps
in order to simplify RPM's build and clarify "supported" functionality.
I see
no future in carrying around functionality that doesn't work as it should
and is "vendor supported" by others here @rpm5.org.
I will rip out the option if it isn't fixed by someone else @rpm5.org
this month.
73 de Jeff
______________________________________________________________________
RPM Package Manager http://rpm5.org
User Communication List rpm-users@rpm5.org
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
______________________________________________________________________
RPM Package Manager http://rpm5.org
User Communication List rpm-users@rpm5.org
