Re: rpm dependency failed because the directory path doesn't exist

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jun 15, 2009 at 9:09 PM, zhang zjmtt <jullyzhang@xxxxxxxxx> wrote:
Hi Guys,

I am using a new version of RPM. It looks like it acts in differently way than before.

What version ? New respect to what ?

If the directory of a file doesn't exist, it will fail the dependency instead of automatically creating the directory.

You are likely using rpm > 4.4.2.x.y.x <> rpm 4.4.6/4.4.7 that reinforce parent-dir/linkto dependency  (good packaging habit want this, some packaging guideline also). See this https://fedoraproject.org/wiki/Packaging:UnownedDirectories
 

For example, abc.rpm contains a file fileDIR/fileNAME. If fileDIR is not installed, abc.rpm will fail the dependency check.

If fileDir have not ownership from other package, well, it is of your package at minimum.
 

Is there any option for rpm or rpmlib to force it automaticaly create the directory?

Put %dir fileDir in your spec file if you think this is correct for your packaging repo clousure.

hth


 

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list


_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux