From: Vagrant Cascadian <vagrant@debian.org>
To: Steve George <steve@futurile.net>
Cc: 70020@debbugs.gnu.org, jlicht@fsfe.org
Subject: [bug#70020] [PATCH v3 1/1] gnu: Add debian-devscripts.
Date: Fri, 03 May 2024 19:42:11 -0700 [thread overview]
Message-ID: <87ikzuwb5o.fsf@wireframe> (raw)
In-Reply-To: <03f2e0ee39ee8112655feccb2a72dc4764c4412b.1713173193.git.steve@futurile.net>
[-- Attachment #1: Type: text/plain, Size: 2434 bytes --]
On 2024-04-15, Steve George wrote:
> * gnu/packages/debian.scm (debian-devscripts): New variable.
>
> Change-Id: Iff64afdb1f730f3d941617bc428a57d09c0381b2
> ---
> gnu/packages/debian.scm | 151 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 151 insertions(+)
>
> diff --git a/gnu/packages/debian.scm b/gnu/packages/debian.scm
> index a88fb04feb..2c79afdc75 100644
> --- a/gnu/packages/debian.scm
> +++ b/gnu/packages/debian.scm
...
> +(define-public debian-devscripts
> + (package
> + (name "debian-devscripts")
As someone who has used devscripts for years (decades?), I would find it
very surprising that it includes a single script! :)
It is essentially a huge grab bag of scripts (most of which I have never
used) ... so I would suggest "debian-devscripts-bts" or simply "debian-bts".
Or packaging more of the scripts? Not sure what would be generally
useful on guix as most are very debian-specific, but I am sometimes
surprised. :)
> + (add-after 'install 'manpage
> + ;; FIXME: missing the man page for bts, how is it created?
I have not quite figured out exactly how it gets there, but according
the last build on debian:
https://buildd.debian.org/status/fetch.php?pkg=devscripts&arch=all&ver=2.23.7&stamp=1702422001&raw=0
it calls:
pod2man --utf8 --center=" " --release="Debian Utilities" bts.pl > bts.1
Presumably this is in one of the scripts/Makefile targets:
%.1: %.pl
podchecker $<
pod2man --utf8 --center=" " --release="Debian Utilities" $< > $@
Seems like they get pulled into SCRIPTS via a wildcard:
PL_FILES := $(wildcard *.pl)
SH_FILES = $(wildcard *.sh)
SCRIPTS = $(patsubst %.pl,%,$(PL_FILES)) $(patsubst %.sh,%,$(SH_FILES))
So it might be possible to get the Makefile to do the right thing ... or
just call pod2man (from "perl") directly since you're only packaging
bts.pl...
> + (synopsis "BTS script from Debian's devscripts")
> + (description "This package only provides the bts script from the Debian
> +devscripts archive. It's useful for Guix Developers that interacting with GNU's
> +debbugs server.")
> + (license license:gpl2)))
This should definitely be changed to gpl2+ looking at scripts/bts.pl and
debian/copyright documents some exceptions; a few of the common files
might actually be a smattering of other licenses; this is where shipping
only a subset is very nice. :)
Hope that is helpful! :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-05-04 2:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 20:41 [bug#70020] [PATCH 1/1] * gnu: Add debian-devscripts Steve George
2024-03-31 21:08 ` Jelle Licht
2024-04-01 20:52 ` [bug#70020] [PATCH v2 0/1] RE: Add Debian-devscripts Steve George
2024-04-01 20:52 ` [bug#70020] [PATCH v2 1/1] * gnu: Add debian-devscripts Steve George
2024-04-15 9:29 ` [bug#70020] [PATCH v3 0/1] RE: Add Debian-devscripts Steve George
2024-04-15 9:29 ` [bug#70020] [PATCH v3 1/1] gnu: Add debian-devscripts Steve George
2024-05-04 2:42 ` Vagrant Cascadian [this message]
2024-05-04 7:06 ` Vagrant Cascadian
2024-05-22 13:44 ` Simon Tournier
2024-05-30 22:07 ` [bug#70020] [PATCH v4 0/1] Add debian-devscripts-bts Steve George
2024-05-30 22:07 ` [bug#70020] [PATCH v4 1/1] gnu: " Steve George
2024-05-31 18:29 ` bug#70020: " Vagrant Cascadian
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=87ikzuwb5o.fsf@wireframe \
--to=vagrant@debian.org \
--cc=70020@debbugs.gnu.org \
--cc=jlicht@fsfe.org \
--cc=steve@futurile.net \
/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).