Github messages for voidlinux
 help / color / mirror / Atom feed
From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] Manual.md: improve automatic depends section, adjust sections hierarchy
Date: Mon, 26 Jun 2023 21:51:37 +0200	[thread overview]
Message-ID: <20230626195137.yxwtcJS1vsZcQubJ8CDgKcScj5v-lg6RnMLSvWfBuGY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44649@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

New review comment by mhmdanas on void-packages repository

https://github.com/void-linux/void-packages/pull/44649#discussion_r1242686916

Comment:
```suggestion
As a special case, `virtual` dependencies may be specified as runtime dependencies in the
`depends` template variable. Several different packages can provide common functionality by
declaring a virtual name and version in the `provides` template variable (e.g.
`provides="vpkg-0.1_1"`). Packages that rely on the common functionality without concern for the
specific provider can declare a dependency on the virtual package name with the prefix `virtual?`
(e.g., `depends="virtual?vpkg-0.1_1"`). When a package is built by `xbps-src`, providers for any
virtual packages will be confirmed to exist and will be built if necessary. A map from virtual
packages to their default providers is defined in `etc/defaults.virtual`. Individual mappings can be
overridden by local preferences in `etc/virtual`. Comments in `etc/defaults.virtual` provide more
information on this map.
```

  parent reply	other threads:[~2023-06-26 19:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 18:45 [PR PATCH] " Chocimier
2023-06-26 19:51 ` [PR REVIEW] " mhmdanas
2023-06-26 19:51 ` mhmdanas
2023-06-26 19:51 ` mhmdanas
2023-06-26 19:51 ` mhmdanas
2023-06-26 19:51 ` mhmdanas
2023-06-26 19:51 ` mhmdanas
2023-06-26 19:51 ` mhmdanas [this message]
2023-06-26 20:08 ` [PR PATCH] [Updated] " Chocimier
2023-06-26 20:09 ` Chocimier
2023-06-26 20:09 ` Chocimier
2023-06-26 20:09 ` Chocimier
2023-06-26 20:09 ` Chocimier
2023-06-26 20:09 ` Chocimier
2023-06-26 20:09 ` Chocimier
2023-06-26 20:25 ` Chocimier
2023-06-26 20:29 ` [PR REVIEW] " Chocimier
2023-06-27  9:37 ` classabbyamp
2023-06-27 10:33 ` Bnyro
2023-07-03 16:06 ` [PR PATCH] [Updated] " Chocimier
2023-07-03 16:07 ` Chocimier
2023-07-03 16:08 ` Chocimier
2023-07-03 16:09 ` [PR PATCH] [Merged]: " Chocimier

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=20230626195137.yxwtcJS1vsZcQubJ8CDgKcScj5v-lg6RnMLSvWfBuGY@z \
    --to=mhmdanas@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).