<p dir="ltr"><br>
On Jul 2, 2015 7:43 AM, "Vít Ondruch" <<a href="mailto:vondruch@redhat.com">vondruch@redhat.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> I am trying to update rubygem-apipie-rails and on that occasion, I'm<br>
> going to unbundle the jquery. I did that by specifying "Requires:<br>
> js-jquery1" and replacing the original file by symlink. And now rpmlint<br>
> complains:<br>
><br>
> rubygem-apipie-rails.noarch: W: dangling-symlink<br>
> /usr/share/gems/gems/apipie-rails-0.3.4/app/public/apipie/javascripts/bundled/jquery-1.7.2.js<br>
> /usr/share/javascript/jquery/1/jquery.js<br>
> The target of the symbolic link does not exist within this package or<br>
> its file<br>
> based dependencies. Verify spelling of the link target and that the<br>
> target is<br>
> included in a package in this package's dependency chain.<br>
><br>
><br>
> I could resolve this by "Requires: %{_jsdir}/jquery/1/jquery.js" and I'd<br>
> love to do it, but this practice is discouraged by guidelines. Now I am<br>
> wondering:<br>
><br>
> 1) Is this reasonable to use the file dependnecy in this case, although<br>
> it is outside of /etc, /bin, /sbin, /usr/bin, or /usr/sbin directories?</p>
<p dir="ltr">Not if you can stop it another way which it appears you do.</p>
<p dir="ltr">> 2) Does this reasoning: "Using file dependencies outside of those<br>
> directories requires yum (and other depsolvers using the repomd format)<br>
> to download and parse a large xml file looking for the dependency."<br>
> still holds with recent move to DNF?</p>
<p dir="ltr">Not unless dnf always downloads the complete filelist repodata. Since dnf is supposed to be faster than yum doubt that it does that. Even if it did doo that it's likely that a future optimization would reestablish this behavior as the complete filelist is so big.</p>
<p dir="ltr">> Isn't time to drop this paragraph?</p>
<p dir="ltr">From the above description it hopefully is apparent that dropping out at this time would be detrimental. <br>
> Isn't this "large xml" downloaded anyway for some reason? </p>
<p dir="ltr">The large file being downloaded contains the complete mapping of packages to the files they contain. This ain't of information is not needed in the majority of cases. Usually the much smaller list of files (and package names and provides) which are contained in the main metadata is sufficient. The files which are in the main metadata are those which are in the directories listed in the guidelines.</p>
<p dir="ltr">> Do we know<br>
> what is the real benefit, if there is some?<br>
></p>
<p dir="ltr">You can look at the sizes of the repo metadata files on a mirror (or in the yum cache if you were unfortunate enough to have to download the filelist for a previous transaction). The savings is avoiding having to download the filelist.</p>
<p dir="ltr">-Toshio</p>