unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicholas von Klitzing via Guix-patches via <guix-patches@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 52530@debbugs.gnu.org
Subject: [bug#52530] [PATCH core-updates-frozen] WIP: Add rust-gtk4 and dependencies
Date: Sat, 08 Jan 2022 09:10:33 +0000	[thread overview]
Message-ID: <v-4Offhbb0Hj4ZsM8U1M8sbbeTMf9rNItsVxTkeZD5IVh4Reh-2j4Rqks-tsFkeQXW4HAsra0_FnjkOgiYFFMwqMQ89xAiT2hAUTXcvn5Ko=@nvk.pm> (raw)
In-Reply-To: <87fsqp433v.fsf@gmail.com>

Hi Maxim,

I was looking reading through the Guix Contributing guide and found that several of the recommendations are not being used by many packages.

For example, many of the packaged rust crates only have a one-line synopsis and a one-line description, where the description is basically just the synopsis with a few extra verbs added.

Is the style mentioned above acceptable or would you recommend I do something else?

Best,
Nicholas

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, December 19th, 2021 at 4:42 AM, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

> Hi Nicholas,
>
> Nicholas von Klitzing nicholas@nvk.pm writes:
>
> > Hello Guix!
> >
> > These are my WIP patches to add the gtk4 crates. Several Gnome and Gtk applications depend on this crate (Authenticator, Fractal, Shortwave, etc).
> >
> > I based the patches on c-u-f because the master branch isn't building on my machine for unrelated reasons I have yet to explore. Regardless, there should be no conflicts.
> >
> > Several of the dependency package definitions are unedited from `guix import`, so please do let me know if you think I should change them.
>
> Yes, the packages need a proper synopsis and description (stylized with
>
> Texinfo) for inclusion. Make sure 'guix lint' is happy with them as
>
> well, and have a read at info '(guix)Contributing', particularly the
>
> 'Synopses andDescriptions' subsection.
>
> Thank you!
>
> Maxim




  reply	other threads:[~2022-01-08  9:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 23:05 [bug#52530] [PATCH core-updates-frozen] WIP: Add rust-gtk4 and dependencies Nicholas von Klitzing
2021-12-19  4:42 ` Maxim Cournoyer
2022-01-08  9:10   ` Nicholas von Klitzing via Guix-patches via [this message]
2023-12-24 15:27 ` [bug#52530] [PATCH] gnu: " Herman Rimm via Guix-patches via
2024-01-22  4:46   ` [bug#52530] [PATCH core-updates-frozen] WIP: " Maxim Cournoyer
2024-01-25 17:47     ` Herman Rimm via Guix-patches via
2024-01-27  3:15       ` bug#52530: " Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='v-4Offhbb0Hj4ZsM8U1M8sbbeTMf9rNItsVxTkeZD5IVh4Reh-2j4Rqks-tsFkeQXW4HAsra0_FnjkOgiYFFMwqMQ89xAiT2hAUTXcvn5Ko=@nvk.pm' \
    --to=guix-patches@gnu.org \
    --cc=52530@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=nicholas@nvk.pm \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).