guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#49329] [PATCH 00/??] Improve Ren'py package


From: Chris Marusich
Subject: [bug#49329] [PATCH 00/??] Improve Ren'py package
Date: Wed, 14 Jul 2021 23:48:25 -0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)

Leo Prikler <leo.prikler@student.tugraz.at> writes:

> Am Samstag, den 10.07.2021, 21:53 -0700 schrieb Chris Marusich:
>> Leo Prikler <leo.prikler@student.tugraz.at> writes:
>> 
>> > * gnu/packages/game-development.scm (python2-renpy)[description]:
>> > Mention,
>> > that it's only used for bootstrapping renpy.
>> > ---
>> >  gnu/packages/game-development.scm | 6 ++++--
>> >  1 file changed, 4 insertions(+), 2 deletions(-)
>> > 
>> > diff --git a/gnu/packages/game-development.scm b/gnu/packages/game-
>> > development.scm
>> > index 22c44a585c..9b231ad333 100644
>> > --- a/gnu/packages/game-development.scm
>> > +++ b/gnu/packages/game-development.scm
>> > @@ -1250,8 +1250,10 @@ developed mainly for Ren'py.")
>> >         ("xdg-utils" ,xdg-utils)))
>> >      (home-page "https://www.renpy.org/";)
>> >      (synopsis "Ren'py python module")
>> > -    (description "This package contains the shared libraries and
>> > Python
>> > -modules of Ren'py.")
>> > +    (description "This package contains the shared libraries and
>> > Python modules
>> > +of Ren'py.  While functional, they are not meaningful on their own
>> > without
>> > +the launcher and common Ren'py code provided by the @code{renpy}
>> > package and
>> > +are only used to bootstrap it.")
>> >      (license license:expat)))
>> >  
>> >  (define-public renpy
>> 
>> LGTM.  If this isn't meant to be installed by users, should it be
>> non-public or perhaps hidden?
> Good point, but I don't think users will accidentally install it like
> they do with gcc.  This description was written to address a point made
> by Ludovic in IRC concerning the package's lack of one.  Having the
> package publicly exported also makes my own life easier when updating
> the recipe.  Last, but not least, these are functional modules and
> could be used to develop code, that depends on Ren'py's internals, but
> none of the "common" renpy stuff (or the common renpy stuff could
> otherwise be extracted from the renpy package and changed to the
> developer's desires).

OK.  I'm fine with that, then.

-- 
Chris

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]