From: Dmitry Alexandrov <dag@gnui.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: excalamus@tutanota.com, Help Guix <help-guix@gnu.org>
Subject: Re: Where to document package relations (was: Playing video in browser)
Date: Fri, 05 Jun 2020 23:53:39 +0300 [thread overview]
Message-ID: <v9k51bfw.dag@gnui.org> (raw)
In-Reply-To: <87367ar57t.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 04 Jun 2020 21:39:02 +0200")
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> It's not very obvious what to document it since it applies to all WebKitGTK.
>
> It's part of the "general software knowledge". For instance, if you install an archiver like `atool', it's your reponsibility to install the backends (unzip, p7zip, etc.) to support the various archive formats. Where to document this?
Normally, in the package relation graph itself.
For instance, in Debian gstreamer1.0-libav and gstreamer1.0-plugins-good are _recommended_ by libwebkit2gtk-* packages. From a user point of view, that means that when he mark epiphany-browser for installing in a package manager, such as aptitude(1), they are marked as well, but, unlike hard dependencies, can be unmarked.
The same applies to atool and its backends, by the way.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2020-06-05 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 15:36 Playing video in browser excalamus--- via
2020-06-04 15:59 ` Pierre Neidhardt
2020-06-04 16:52 ` excalamus--- via
2020-06-04 19:39 ` Pierre Neidhardt
2020-06-04 21:36 ` excalamus--- via
2020-07-08 10:40 ` Pierre Neidhardt
2020-06-05 20:53 ` Dmitry Alexandrov [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=v9k51bfw.dag@gnui.org \
--to=dag@gnui.org \
--cc=excalamus@tutanota.com \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).