search for: __find_requires

...e %prep stage of the spec files, something like > this after the initial %setup macro: > > perl -pi -e 's:^#!/usr/bin/r:#!/usr/bin/R: unless $i++' > path/to/R/scripts/*.R > > > Peter > _______________________________________________ > Peter and Leon The %define __find_requires %{nil} sounds too disruptive. I'll look at scripting the corrections. Maybe I will request at EPEL to see they would consider making a link to /usr/bin/r. However I checked a Debian installation, and it's not there either. So I don't know what the creators of the CRAN package are targ...

...docs # Only > RH 8.0 seems to care here echo "rpm_version == %{rpm_version}" if [ "%{rpm_version}" == "42" ]; then %define __perl_requires %{SOURCE999} echo "%{__perl_requires}" elif [ "%{rpm_version}" == "41" ]; then %define __find_requires %{SOURCE998} echo "%{__find_requires}" fi

...able in this case. My question therefore is - how can I tell rpmbuild to stop automatically creating a dependency list? The best I can come up with at the moment is to add the following to my ~/.rpmmacros (line numbers added by me): [1] %__os_install_post /usr/lib/rpm/brp-strip-comment-note [2] %__find_requires /bin/true [3] %__perl_requires /bin/true So: [1] - Stop it stripping already stripped binaries. [2] and [3] - This stops it doing the automatic dependency list creation. This seems a bit heavy handed though, is there another, cleaner way to do it? Regards, Fred.

Thanks for the suggestion, but after putting that at the top of the spec and running rpmbuild, I still get Resolving Dependencies --> Running transaction check ---> Package R-RPostgreSQL.x86_64 0:0.4-1.el6 will be installed --> Processing Dependency: /usr/bin/r for package: R-RPostgreSQL-0.4-1.el6.x86_64 --> Processing Dependency: /usr/bin/r for package:

Hi. I googled for this thoroughly but couldn''t find any module that actually worked. Is there any good puppet module or manifest for installing Sun JDK? Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to

This is not specifically a CentOS question, but I am creating RPMS for CentOS 6 from some CRAN tarballs. I run R2spec -s tarball to create a spec file, and most of the time it works ok, but sometimes (RPostgresSQL, Rcpp for example) the package has test or example programs that start with #!/usr/bin/r with lower case r, and the resulting package then winds up with a dependency on /usr/bin/r,