From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [RFC]: vdummy shortcut for transitional packages
Date: Wed, 14 Sep 2022 00:10:58 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39272@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
New issue by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/39272
Description:
Every transitional package has at least these 3 common variables:
* `build_style=meta` - otherwise the build would fail because of an empty package
* `depends=...` - usually `${sourcepkg}>=${version}_${revision}`, but often `${version}_${revision}` is left out or `${sourcepkg}` is replaced by something else, for example `${sourcepkg}-devel`
* `short_desc+=" transitional package"` or an equivalent, many versions currently exist in packages
a few examples:
```
antimicro_package() {
build_style=meta
depends="${sourcepkg}"
short_desc+=" - transitional dummy package"
}
```
```
Gifsicle_package() {
depends="gifsicle"
short_desc+=" (transitional dummy package)"
build_style=meta
}
```
This is a proposal for a vdummy function that fills these variables for the packager, for example:
```
antimicro_package() {
vdummy ${sourcepkg}
}
```
`vdummy` should take one argument - the package name and use it in `$depends` - `depends="$1>=${version}_${revision}"`. `vdummy` will also unify `$short_desc` for transitional packages, I would propose to use the ` - (transitional dummy package)` style.
next reply other threads:[~2022-09-13 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 22:10 paper42 [this message]
2022-09-13 22:13 ` classabbyamp
2022-09-14 12:29 ` Anachron
2022-09-14 22:50 ` paper42
2022-09-14 22:52 ` paper42
2022-12-14 2:01 ` github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39272@inbox.vuxu.org \
--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).