Re: [Rd] Issue tracking in packages [was: Re: [R] change in read.spss, package foreign?]
On 9/10/05, Thomas Lumley [EMAIL PROTECTED] wrote: On Sat, 10 Sep 2005, Gabor Grothendieck wrote: On 9/10/05, Thomas Lumley [EMAIL PROTECTED] wrote: On Sat, 10 Sep 2005, Gabor Grothendieck wrote: And one more comment. The DESCRIPTION file does not record the location or existence of the various subdirectories such as R, man, exec, etc. If NEWS is to be recorded as a meta data line item in DESCRIPTION then surely all of these should be too so its symmetric and they are all on an equal footing (or else none of them should be, which in fact I think is preferable). I don't see any advantage in symmetry. The locations of these The present discussion is where the change information may be located but that is also true of the source and other information.We could just as easily have a field in the DESCRIPTION that tells the build where to find the R source. Its really the same issue. There are two important differences 1/ No existing package has it source anywhere other than in the R subdirectory. Existing packages have their change logs in different places and different formats. In terms of the source package the source code is in the R subdirectory because its been standardized that way and the R CMD tools support it. It could, in principle be anywhere and brought into the built package at build time had it not been designed that way. The same is true of the change information. The point is that there is really no difference in principle between the two. Furthermore, what existing packages do is not important since its no harder and probably easier to adapt to the standard scheme. Even if that were not the case I don't think that that should drive the design. 2/ Having source code where it will not be found must be an error -- making the source code available to R *cannot* be optional. Making a change log available *must* be optional. Source code is optional too. One can create a package with no R subdirectory. In fact the only thing you cannot leave out and still pass R CMD check is the DESCRIPTION file. There really is no difference between change information and the source. Both could be in the source package or not in the source package and just brought into the built package at build time depending on how the build process is designed. Also in both cases the advantage of having everything in the source package is that the built package can be guaranteed to be built from the source package. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] FreeBSD 7.0-CURRENT and R-2.2.0 alpha
These were found by AC_CHECK_FUNCS (please confirm what configure said) so most likely some macro needs to be set or header included. Could you please find out how configure managed to find cpow etc when they appear not to be in libc/libm? On Sat, 10 Sep 2005, Rainer Hurling wrote: The configure script runs fine, but when I compile todays alpha version of R-2.2.0 (R-alpha_2005-09-10_r35546.tar.gz) under FreeBSD 7.0-CURRENT from Sept. 4th I get the following output: [...] gcc -I../../src/extra/zlib -I../../src/extra/bzip2 -I../../src/extra/pcre -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -D__NO_MATH_INLINES -g -O2 -c version.c -o version.o gcc -I../../src/extra/zlib -I../../src/extra/bzip2 -I../../src/extra/pcre -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -D__NO_MATH_INLINES -g -O2 -c vfonts.c -o vfonts.o f77 -g -O2 -c xxxpr.f -o xxxpr.o gcc -export-dynamic -L/usr/local/lib -o R.bin Rmain.o CConverters.o CommandLineArgs.o Rdynload.o Renviron.o RNG.o apply.o arithmetic.o apse.o array.o attrib.o base.o bind.o builtin.o character.o coerce.o colors.o complex.o connections.o context.o cov.o cum.o dcf.o datetime.o debug.o deparse.o deriv.o dotcode.o dounzip.o dstruct.o duplicate.o engine.o envir.o errors.o eval.o format.o fourier.o gevents.o gram.o gram-ex.o graphics.o identical.o internet.o iosupport.o lapack.o list.o logic.o main.o mapply.o match.o memory.o model.o names.o objects.o optim.o optimize.o options.o par.o paste.o pcre.o platform.o plot.o plot3d.o plotmath.o print.o printarray.o printvector.o printutils.o qsort.o random.o regex.o registration.o relop.o saveload.o scan.o seq.o serialize.o size.o sort.o source.o split.o sprintf.o startup.o subassign.o subscript.o subset.o summary.o sysutils.o unique.o util.o version.o vfonts.o xxxpr.o ../unix/libunix.a ../appl/libappl.a ../nmath/libnmath.a -lf77blas -latlas -lg2c -lm ../extra/zlib/libz.a ../extra/bzip2/libbz2.a ../extra/pcre/libpcre.a /usr/local/lib/libintl.so -Wl,-rpath -Wl,/usr/local/lib -lreadline -lm -liconv complex.o(.text+0x106): In function `mycpow': /usr/local/R-alpha/src/main/complex.c:170: undefined reference to `cpow' complex.o(.text+0x6f9): In function `do_cmathfuns': /usr/local/R-alpha/src/main/complex.c:323: undefined reference to `carg' complex.o(.text+0xb4b): In function `z_log': /usr/local/R-alpha/src/main/complex.c:423: undefined reference to `clog' complex.o(.text+0xb86): In function `z_logbase': /usr/local/R-alpha/src/main/complex.c:429: undefined reference to `clog' complex.o(.text+0xb98):/usr/local/R-alpha/src/main/complex.c:429: undefined reference to `clog' complex.o(.text+0xbd8): In function `z_exp': /usr/local/R-alpha/src/main/complex.c:434: undefined reference to `cexp' complex.o(.text+0xbf8): In function `z_sqrt': /usr/local/R-alpha/src/main/complex.c:439: undefined reference to `csqrt' complex.o(.text+0xc18): In function `z_cos': /usr/local/R-alpha/src/main/complex.c:486: undefined reference to `ccos' complex.o(.text+0xc38): In function `z_sin': /usr/local/R-alpha/src/main/complex.c:491: undefined reference to `csin' complex.o(.text+0xc5e): In function `z_tan': /usr/local/R-alpha/src/main/complex.c:497: undefined reference to `ctan' complex.o(.text+0xd26): In function `z_atan2': /usr/local/R-alpha/src/main/complex.c:523: undefined reference to `catan' complex.o(.text+0xe18): In function `z_asin': /usr/local/R-alpha/src/main/complex.c:541: undefined reference to `casin' complex.o(.text+0xe38): In function `z_acos': /usr/local/R-alpha/src/main/complex.c:553: undefined reference to `cacos' complex.o(.text+0xe58): In function `z_atan': /usr/local/R-alpha/src/main/complex.c:559: undefined reference to `catan' complex.o(.text+0xe78): In function `z_acosh': /usr/local/R-alpha/src/main/complex.c:564: undefined reference to `cacosh' complex.o(.text+0xe98): In function `z_asinh': /usr/local/R-alpha/src/main/complex.c:569: undefined reference to `casinh' complex.o(.text+0xeb8): In function `z_atanh': /usr/local/R-alpha/src/main/complex.c:574: undefined reference to `catanh' complex.o(.text+0xed8): In function `z_cosh': /usr/local/R-alpha/src/main/complex.c:579: undefined reference to `ccosh' complex.o(.text+0xef8): In function `z_sinh': /usr/local/R-alpha/src/main/complex.c:584: undefined reference to `csinh' complex.o(.text+0xf18): In function `z_tanh': /usr/local/R-alpha/src/main/complex.c:589: undefined reference to `ctanh' *** Error code 1 Stop in /usr/local/R-alpha/src/main. *** Error code 1 Stop in /usr/local/R-alpha/src/main. *** Error code 1 Stop in /usr/local/R-alpha/src. *** Error code 1 Stop in /usr/local/R-alpha. Am I missing something? Thank you, Rainer Hurling __ R-devel@r-project.org
Re: [Rd] Issue tracking in packages [was: Re: [R] change in read.spss, package foreign?]
On Sat, 10 Sep 2005 19:06:51 +0200, Martin Maechler (MM) wrote: TL == Thomas Lumley [EMAIL PROTECTED] on Sat, 10 Sep 2005 09:32:29 -0700 (PDT) writes: Standard location or a mechachanism like the one you describe are both similar amount of work (and not much at all), the HTML pages are generated by perl and I have the parsed DESCRIPTION file there, i.e., using a fixed name or the value of the Changelog field is basically the same. TL In which case a Changlog entry in DESCRIPTION would be a TL very nice addition, and would have the advantage of not TL requiring changes to packages. yes *and* does allow slightly more flexibility with almost no cost, as Fritz confirmed. Well, as Kurt pointed out in another (?) thread CRAN is not the R universe, and, e.g., Seth might have another opinion when it comes to BioC administration. But I don't think you can (or should) do too much sensible computations on packages without having parsed the DESCRIPTION file, so the almost no cost statement should be pretty safe. And, BTW, Gabor, NEWS and ChangeLog are not at all the same thing and it would be silly to urge users to one of them. At least 'ChangeLog' is a well defined format for emacs users that can very quickly be updated semi-automagically (C-x 4 a when you're in file foo.R with function myfun(.) autogenerates a neat entry in a ChangeLog file); but then really people should be allowed to use other formats for good reasons. I fully agree. .f __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
