From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] request to update sfeed from 1.0 to 1.2
Date: Fri, 11 Feb 2022 14:28:39 +0100 [thread overview]
Message-ID: <20220211132839.ipKd23f0BGih5swQuakPbxfJPt5UtE32SxE0d9oq5Bo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35521@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
Closed issue by hiltjo on void-packages repository
https://github.com/void-linux/void-packages/issues/35521
Description:
Please update sfeed from 1.0 to 1.2. It has many improvements.
sfeed_curses is merged inside the sfeed repository and so the separate sfeed_curses package can be deprecated.
The current maintainer doesn't seem to respond by e-mail for whatever reason (1.1 request was ignored).
For maintainers, this feed can be useful to track releases:
https://git.codemadness.org/sfeed/tags.xml
Concept template for 1.2:
# Template file for 'sfeed'
pkgname=sfeed
version=1.2
revision=1
build_style=gnu-makefile
make_use_env=compliant
make_install_args="MANPREFIX=/usr/share/man"
makedepends="ncurses-devel"
depends="curl ncurses"
short_desc="RSS and Atom parser"
maintainer="someone"
license="ISC"
homepage="https://git.codemadness.org/sfeed"
distfiles="https://codemadness.org/releases/sfeed/sfeed-${version}.tar.gz"
checksum=7d3cdaf8dcc6582f6655330f82f8a57ca37c4b9c84ff995b09b7b7fb9fe58b58
conflicts="sfeed_curses"
provides="sfeed_curses-0.1_1"
post_install() {
vlicense LICENSE
vdoc README
}
next prev parent reply other threads:[~2022-02-11 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 23:35 [ISSUE] " hiltjo
2022-02-11 13:28 ` paper42
2022-02-11 13:28 ` paper42 [this message]
2022-02-11 13:29 ` paper42
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220211132839.ipKd23f0BGih5swQuakPbxfJPt5UtE32SxE0d9oq5Bo@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).