Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: xbps-src: have cmdline arguments take precedence over config files
Date: Wed, 12 Feb 2020 14:12:03 +0100	[thread overview]
Message-ID: <20200212131203.xK7blj3iMYZ5aVBOB44nePik462M8DDGHi0owyypv7A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19055@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

xbps-src: have cmdline arguments take precedence over config files
https://github.com/void-linux/void-packages/pull/19055

Description:
This way we can e.g. have `XBPS_MAKEJOBS` set in config file while overriding it with `-j`.

This also notably changes some other semantics. Particularly:

1) Links in `hostdir`/`masterdir` are now always resolved regardless of how they are provided (via arg or via config)
2) The `-o` option for `xbps-src` specifying build options merges with whatever was previously specified in config file, instead of overriding. This makes more sense overall as options specified on command line
actually apply to every package built during that run.

This PR is in preparation for support for custom configurations via `-c configname`.

      parent reply	other threads:[~2020-02-12 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19055@inbox.vuxu.org>
2020-02-12 12:10 ` voidlinux-github
2020-02-12 12:12 ` voidlinux-github
2020-02-12 12:13 ` voidlinux-github
2020-02-12 12:14 ` voidlinux-github
2020-02-12 12:14 ` voidlinux-github
2020-02-12 12:21 ` voidlinux-github
2020-02-12 13:12 ` voidlinux-github [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

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

  git send-email \
    --in-reply-to=20200212131203.xK7blj3iMYZ5aVBOB44nePik462M8DDGHi0owyypv7A@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).