public inbox for
 help / color / mirror / Atom feed
From: Federico Kircheis <>
To: Jon Turney <>,
	"" <>
Subject: Re: [ITP] dumpasn1
Date: Sat, 14 May 2022 14:58:36 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 14 May 2022 13:24:08 UTC, Jon Turney <> wrote:
>On 11/05/2022 20:20, Federico Kircheis wrote:
>> Hello to everyone,
>> I'm interested in becoming a package maintainer for the program dumpasn1.
>> (see and
>> It would be a new package for the cygwin distribution, but it is already
>> distributed on different systems, like Arch, Debian, Fedora, openSUSE,
>> Gentoo and many others
>> .hint and .cygport files are attached
>> As the name implies, it is a program for dumping data encoded using the ASN.1 encoding rules
>Thanks. I added this to your authorized packages.
>A few small comments on the cygport
>> SRC_URI="${VERSION}.orig.tar.gz"
>I'm not sure that '' isn't the correct SRC_URI.
>The debian packaging contains a manpage, which it might be useful to incorporate.
>> PKG_NAMES="dumpasn1"
>None of these are necessary, I think.

I've used the debian package ad it is a package that contains everything for creating the cygwin package (source+config), and provides a versioned source.

The URL you suggested is only the source file, and to be honest I do not know how to write the corresponding cygport file.
It also does not seem to be versioned.

Thus I would prefer to use the Debian source if it is not an issue.

I'll try removing the variables you mentioned.

  reply	other threads:[~2022-05-14 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 19:20 Federico Kircheis
2022-05-14 13:24 ` Jon Turney
2022-05-14 14:58   ` Federico Kircheis [this message]
2022-05-15 15:18     ` Jon Turney

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:

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

  git send-email \ \ \ \ \

* 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.
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).