unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: phodina <phodina@protonmail.com>, 55827@debbugs.gnu.org
Subject: [bug#55827] [PATCH] gnu: Add kismet.
Date: Fri, 10 Jun 2022 17:30:37 +0200	[thread overview]
Message-ID: <22cbe81eefd1b952e0f233256fb5521df6133985.camel@telenet.be> (raw)
In-Reply-To: <DYTQMUydfrTj6_0ZVa_f2x-7yRzWANjbC0EXV50UqwCLyAt-OCA9eMiZ69CfErY-wu2Mk_x76YGD-C0zG2j_bo5DLyhIuD9Jmk-1GzzgPzQ=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]

phodina via Guix-patches via schreef op di 07-06-2022 om 07:41 [+0000]:
> Hi,
> 
> this patch adds Kismet package.
> 
> ----
> Petr

I have looked at how other distros package it:

* http://deb.debian.org/debian/pool/main/k/kismet/kismet_2016.07.R1-1.debian.tar.xz

  has a fix_manpage, fix_typos patch, openssl_1.1.0.
  The 'copyright' file that says some of it is gpl-2-only or BSD3.
  Adds a .desktop file.
  Are they still relevant for the 2022 version?

* fedora has a patch

  https://src.fedoraproject.org/rpms/kismet/blob/rawhide/f/kismet-install.patch

  is it relevant to Guix?

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      parent reply	other threads:[~2022-06-10 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  7:41 [bug#55827] [PATCH] gnu: Add kismet phodina via Guix-patches via
2022-06-07  7:50 ` Maxime Devos
2022-06-07  8:06 ` Maxime Devos
2022-06-07  9:57   ` [bug#55827] [PATCH v2] " phodina via Guix-patches via
2022-06-07 11:04     ` Maxime Devos
2022-06-10  8:44       ` phodina via Guix-patches via
2022-06-15 20:19         ` bug#55827: [PATCH] " Ludovic Courtès
2022-06-10 15:30 ` Maxime Devos [this message]

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=22cbe81eefd1b952e0f233256fb5521df6133985.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55827@debbugs.gnu.org \
    --cc=phodina@protonmail.com \
    /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).