similar to: Compress::Raw::Zlib no longer installed with Perl on Fedora 30?

I can confirm: [spot at localhost ~]$ rpm -q perl --requires |grep Zlib perl-Compress-Raw-Zlib perl-IO-Zlib [spot at localhost ~]$ rpm -q perl perl-5.28.2-436.fc30.x86_64 It would require either notable human intervention (or a canceled mid-upgrade state) for a Fedora 30 system to end up with perl, but not perl-Compress-Raw-Zlib. Thanks, Tom On Wed, Jul 24, 2019 at 8:42 AM Marc Schwartz

> On Jul 23, 2019, at 1:04 PM, Marc Schwartz <marc_schwartz at me.com> wrote: > > Hi, > > I had an issue report from a user of my WriteXLS CRAN package indicating that Compress::Raw::Zlib is apparently not installed by default with Perl on Fedora 30. > > Since this appears to be a new issue, I am wondering if one of the Fedora maintainers on this list can confirm this

> On Nov 6, 2017, at 3:23 AM, Kamlesh Khollam <khollam.kamlesh33 at gmail.com> wrote: > > Hi Team, > I am tried "WriteXLS" package for merging 2 csv files. R script runs > successfully but does not create CSVmerge file. > > Appreciate our help. > > ?Best Regards, > Kamlesh Khollam? Hi, You appear to be replying to a thread from January of 2016, or

Hi Team, I am tried "WriteXLS" package for merging 2 csv files. R script runs successfully but does not create CSVmerge file. Appreciate our help. ?Best Regards, Kamlesh Khollam? [[alternative HTML version deleted]]

Folks, I'd like to get expert's opinion on which compression level is suitable for lld's -compress-debug-section=zlib option, which let the linker compress .debug_* sections using zlib. Currently, lld uses compression level 9 which produces the smallest output in exchange for a longer link time. My question is, is this what people actually want? We didn't consciously choose

I am working on creating a program for some simulations I need to do and I want to execute a Perl script that I wrote using the system() command in R. I have spent a couple days trying to figure this out and it appears that my problem occurs when sending the perl script file path through R to MSDOS. I have tried using double backslashes, quotations, etc. Moving my files to the root directory with

Also not an expert, but would it make sense for this to be configurable at a fine-grained level, perhaps with another option, or an extension to the compress-debug-sections switch interface? That way users who care about the finer details can configure it themselves. And we should pick sensible options for the default. James On 2 August 2018 at 11:08, Pavel Labath via llvm-dev < llvm-dev at

Hello everyone, Is it possible to configure the zlib plugin to compress the emails in one folder only? I would like to compress the emails when they are stored in my 'Archives' folders and sub folders. Thanks, Andr? Rodier.

Hello, is it possible to compress by zlib only selected folders? My e-mail accounts have archive folder and this folder contains old comunications with my customers and this I use very rare, so I want to compress them by zlib to save space. Is this possible? Thanks, Filip Bartmann

Hi, My R package has files in the 'inst' directory that it needs to reference. How can the R scripts in my package find out the full path to the 'inst' directory after the package is installed, given that different users may have installed the package to different libraries? Thanks, Jon Malmaud

Hi all, There have been quite a few threads in the recent months pertaining to the ability to directly write native Excel (.xls) files from R. For example, exporting R matrices and/or data frames to an Excel file, with perhaps the ability to create multiple tabs (worksheets) within a single file, with one tab/sheet per R object. There exists the xlsReadWrite package on CRAN by Hans-Peter Suter,

Hi Rui, What's the intended advantage for compressing the debug sections? - (i) Improved link time through smaller IO / (ii) Improved Load / startup time for the debugger / (iii) Smaller exe with debug info for distribution / disk space? For i) and ii) how much this is worth it depends on balance of storage bandwidth to compression (i) / decompression (ii) bandwidth. For spinning drives it

> As to (3), in most cases, I believe it is rare to distribute executables with debug info widely > I think it is at least less important than (1). Agreed. > I think (1) is definitely the case, and that's also true for a distributed build system with which a lot of object files are copied between machines. > My suggestion was to use compression level 9 when both -O2 and

Not really, as well as some sensitivity to the input data overall performance of the link with compression will depend on how this is implemented in lld - how is it parallelized? How is it chunked? Is it effectively pipelined with IO? Or, I wouldn't feel comfortable being able to make a recommendation to our end-users on whether to use this option or not based on my existing extensive

I tried installing fedora grpc srpm on CentOS and ran into following error when installing srpm. I understand fedora makes use of more recent versions of openssl, glibc etc but why should this happen when installing source rpm? Any pointers/articles on how to go about building fedora srpms on CentOS? Any way out other than building directly using sources? rpm -i grpc-1.17.1-3.fc30.i686.rpm

I am using R 2.11.1 in a Microsoft Windows 7 environment.   I tried using WriteXLS, but get the message " In system(cmd) : perl not found"   What is the "easiest" way to write an R dataframe to Excel?  (I am familiar with WriteXLS, but I do not have PERL installed, and if not needed, do not wish to install it.)   I am also familiar with write.table, but if possible, wish to

Hi all, For several years, I have used path.package() to get the path to Perl scripts contained within WriteXLS. I have a request to change this to using system.file(), which would provide the ability to utilize WriteXLS functionality, without having to load the package, which path.package() requires. Based upon my review of the code, I don't see any obvious down sides to making the change,

Dear All, I think I am confused about how I'd be able to use zlib starting with R 2.7.0. I just downloaded the latest development version, built it, etc, but I am not able to find the zlib.h that, I believe, R should place somewhere under "where/you/want/R/to/go" (from --prefix=/where/you/want/R/to/go). There seem to be entry points for zlib in the binary (e.g., grep -r gzopen ./

Dear All, I am using WriteXLS to write tables with multiple sheets with the command: WriteXLS("tables", ExcelFileName = fileName, SheetNames = tableList, perl = "perl", verbose = FALSE, Encoding = c("UTF-8", "latin1"), row.names = TRUE, col.names = TRUE, AdjWidth = TRUE, AutoFilter = FALSE, BoldHeaderRow = FALSE,

With all due respect to the various people, their hard work and associated repos, where is the best place to do a yum install for these two packages below in regards to an internet facing production Centos 4.4 server perl-IO-Zlib perl-Archive-Tar I noticed dag and karan repos appear to have it and my experience and research tells me that using CPAN is not an option for possible problems at