GNU bug report logs -
#32699
Adding r-gtk2 and other packages for r-qda (RFC)
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32699 in the body.
You can then email your comments to 32699 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#32699
; Package
guix-patches
.
(Tue, 11 Sep 2018 12:41:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Pjotr Prins <pjotr.public12 <at> thebird.nl>
:
New bug report received and forwarded. Copy sent to
guix-patches <at> gnu.org
.
(Tue, 11 Sep 2018 12:41:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Attached a bunch of packages I wrote for RQDA. This is a particular
useful package because it depends on GTK2. guix import cran is pretty
awesome - it got most of it right :).
One or two hacks in there to disable X11 tests. Anyone any comments on
how to enable X11 instead of having X-headless? And is this good
enough to submit to Guix otherwise?
Pj.
[r-qda.patch (text/x-diff, attachment)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#32699
; Package
guix-patches
.
(Wed, 12 Sep 2018 08:51:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 32699 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Added another patch for text mining with R tm.
I would appreciate some feedback on the previous patch before I start
submitting.
Pj.
[tm.patch (text/x-diff, attachment)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#32699
; Package
guix-patches
.
(Thu, 13 Sep 2018 12:56:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 32699 <at> debbugs.gnu.org (full text, mbox):
Hi Pjotr,
thanks for the patches!
I’m glad that you found the recursive importer helpful. Unfortunately,
it doesn’t do a great job with licenses: some of the packages have a
list of GPLv2+ and GPLv3+. Sometimes this is really just a CRAN
expansion for “GPLv2 or later”, other times it means that different
parts of the package are under different licenses.
Could you please check what the license list means for r-rgtk2 and
r-cairodevice? In some cases we can replace the list with a single
license; in other cases we add a comment above the license field to
state what it really means.
Generally, I would recommend putting these packages in (gnu packages
cran) instead of (gnu packages statistics). I’ve been moving packages
from statistics.scm to cran.scm to avoid circular dependencies between
modules.
Here some more comments and questions about the patches:
* the importer unfortunately still defaults to generating HTTP URLs for
the home page instead of HTTPS. It also fails to add a trailing slash
for cran.r-project.org URLs. Could you please add them? (This keeps
the linter happy.)
* the description of many R packages on CRAN don’t use full sentences,
whereas for Guix we’d like to use complete sentences. The easiest way
to fix this is to add “This package provides” to the beginning of the
package description from CRAN. (The importer does this automatically,
when the description begins with “A ”, but it can’t easily guess other
instances where this would be appropriate.)
* the synopses of R packages from CRAN often use … “creative” letter
casing. Instead of, say, “R Bindings for Gtk 2.8.0 and Above” we
would use “R bindings for Gtk 2.8.0 and above”. (I don’t know how to
let the importer do the right thing automatically.)
* for r-cairodevice we might be able to run the tests after setting up
an X server in a pre-check build phase. We would need to add
("xorg-server" ,xorg-server) to the native inputs. Here’s an example
for the phase taken from the caja package:
--8<---------------cut here---------------start------------->8---
#:phases
(modify-phases %standard-phases
(add-before 'check 'pre-check
(lambda _
;; Tests require a running X server.
(system "Xvfb :1 &")
(setenv "DISPLAY" ":1")
;; For the missing /etc/machine-id.
(setenv "DBUS_FATAL_WARNINGS" "0")
#t)))
--8<---------------cut here---------------end--------------->8---
* the description in r-cairodevice includes references to code: we
would, for example, replace “arbitrary GdkDrawable or Cairo context”
with “arbitrary @code{GdkDrawable} or @code{Cairo} context”. Same
with “RGtk2” and “getGraphicsEvent()”.
* I would replace the description of “r-gwidgets” with this text:
"gWidgets provides a toolkit-independent API for building
interactive GUIs. At least one of the toolkit implementations for
a specific GUI backend (such as @code{gWidgetsRGtk2}) should be
installed."
* In r-gwidgetsrgtk2 we might be able to do without patching the
DESCRIPTION and NAMESPACE files by adding a pre-check phase as shown
above. Is there another reason for patching this file?
* I would change the r-gwidgetsrgtk2 description to this (taken from the
package documentation):
“This package allows the gWidgets API to use the RGtk2 package
allowing the use of the GTK libraries within R.”
* r-igraph already exists in (gnu packages graph).
* r-rqda uses sources from a git checkout, which means that you could
use git-specific helpers:
(version (git-version "0.3-1" revision commit))
…
(file-name (git-file-name name version))
Note that the revision is just a Guix-internal number (as a string)
starting at "1".
* r-nlp: the same applies as for other packages: please add it to
cran.scm, use HTTPS and a trailing slash for the home-page field, use
lower case for the synopsis, and expand the description to a complete
sentence.
* r-tm looks fine to me.
To generate patches more easily you can create one local commit per
package and then use git format-patch -5 to create 5 patch files for the
last 5 commits. We usually apply one patch per package.
--
Ricardo
Owner recorded as Ricardo Wurmus <rekado <at> elephly.net>.
Request was from
Ricardo Wurmus <rekado <at> elephly.net>
to
control <at> debbugs.gnu.org
.
(Thu, 13 Sep 2018 17:03:01 GMT)
Full text and
rfc822 format available.
Information forwarded
to
guix-patches <at> gnu.org, Ricardo Wurmus <rekado <at> elephly.net>
:
bug#32699
; Package
guix-patches
.
(Wed, 23 Mar 2022 15:48:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 32699 <at> debbugs.gnu.org (full text, mbox):
Hi Ricardo,
Digging this old patch [1], well considering that running now “guix
import cran -r” for the second submission:
+ (name "r-nlp“)
+ (version "0.1-11")
+ (name "r-tm")
+ (version "0.7-5")
the result is:
(name "r-nlp")
(version "0.2-1")
(name "r-tm")
(version "0.7-8")
For the others:
+(define-public r-rgtk2
+ (package
+ (name "r-rgtk2")
+ (version "2.20.35")
Not in CRAN anymore.
+(define-public r-cairodevice
+ (package
+ (name "r-cairodevice")
+ (version "2.25")
Not in CRAN anymore.
+(define-public r-gwidgets
+ (package
+ (name "r-gwidgets")
+ (version "0.0-54")
Not in CRAN anymore.
+(define-public r-gwidgetsrgtk2
+ (package
+ (name "r-gwidgetsrgtk2")
+ (version "0.0-86")
Not in CRAN anymore.
+(define-public r-igraph
+ (package
+ (name "r-igraph")
+ (version "1.2.2")
Current Guix:
name: r-igraph
version: 1.2.11
+(define-public r-rqda
+ (let ((commit "3cd9abbbde590e1bf9c602b427ebd49e43b6b71a")
+ (revision "0.3-1"))
+ (package
Not in CRAN anymore.
On Thu, 13 Sep 2018 at 14:55, Ricardo Wurmus <ricardo.wurmus <at> mdc-berlin.de> wrote:
> Here some more comments and questions about the patches:
[...]
> To generate patches more easily you can create one local commit per
> package and then use git format-patch -5 to create 5 patch files for the
> last 5 commits. We usually apply one patch per package.
Reading your comments, I propose therefore to drop this patch in favor
of another recent submission one (I or you if you beat me :-)) could do
later after this email.
WDYT?
1: <http://issues.guix.gnu.org/issue/32699>
Cheers,
simon
Information forwarded
to
guix-patches <at> gnu.org, Ricardo Wurmus <rekado <at> elephly.net>
:
bug#32699
; Package
guix-patches
.
(Fri, 06 May 2022 11:27:01 GMT)
Full text and
rfc822 format available.
Message #19 received at 32699 <at> debbugs.gnu.org (full text, mbox):
zimoun <zimon.toutoune <at> gmail.com> writes:
> Reading your comments, I propose therefore to drop this patch in favor
> of another recent submission one (I or you if you beat me :-)) could do
> later after this email.
>
>
> WDYT?
Sounds good.
--
Ricardo
Reply sent
to
Clément Lassieur <clement <at> lassieur.org>
:
You have taken responsibility.
(Tue, 07 Nov 2023 14:24:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Pjotr Prins <pjotr.public12 <at> thebird.nl>
:
bug acknowledged by developer.
(Tue, 07 Nov 2023 14:24:02 GMT)
Full text and
rfc822 format available.
Message #24 received at 32699-done <at> debbugs.gnu.org (full text, mbox):
On Fri, May 06 2022, Ricardo Wurmus wrote:
> zimoun <zimon.toutoune <at> gmail.com> writes:
>
>> Reading your comments, I propose therefore to drop this patch in favor
>> of another recent submission one (I or you if you beat me :-)) could do
>> later after this email.
>>
>>
>> WDYT?
>
> Sounds good.
Hi, closing since r-nlp, r-tm and r-igraph are already packaged.
Cheers,
Clément
Added tag(s) wontfix.
Request was from
Clément Lassieur <clement <at> lassieur.org>
to
control <at> debbugs.gnu.org
.
(Tue, 07 Nov 2023 14:25:01 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 06 Dec 2023 12:24:08 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 155 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.