From: lfdebrux <lfdebrux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Setting default command line options in etc/conf isn't working
Date: Fri, 28 Jan 2022 09:18:06 +0100 [thread overview]
Message-ID: <20220128081806.to9oiBeLOROS4tL7IdwNLgMYbvdC3sMf-1uPnHHJUHk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35139@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
Closed issue by lfdebrux on void-packages repository
https://github.com/void-linux/void-packages/issues/35139
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: `Void 5.11.22_1 x86_64-musl GenuineIntel uptodate rFFF`
* package: `xbps-src`
### Expected behavior
Setting an option in `etc/conf` should have the same effect as calling `xbps-src` with a command line parameter, as documented in `xbps-src`:
https://github.com/void-linux/void-packages/blob/5f589a9962d7871deedbaa3d3e92751ace5ef1d6/xbps-src#L365-L367
### Actual behavior
Some options don't have any effect. I think this is because they get lost when the chroot is entered, because they aren't added to `XBPS_OPTIONS` or `$XBPS_MASTERDIR/etc/xbps/xbps-src.conf`.
### Steps to reproduce the behavior
For example, if I want to avoid adding `-a armv5tel-musl` to the command line every time:
1. Checkout latest version of void-linux/void-packages
2. Add file `etc/conf` with contents `XBPS_CROSS_BUILD=armv5tel-musl`
3. Run `xbps-src pkg base-files`
I expect it to build a package for `armv5tel-musl`, instead it builds a package for `x86_64-musl` (the native arch).
prev parent reply other threads:[~2022-01-28 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 16:57 [ISSUE] " lfdebrux
2022-01-20 20:11 ` Chocimier
2022-01-28 8:17 ` lfdebrux
2022-01-28 8:18 ` lfdebrux [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=20220128081806.to9oiBeLOROS4tL7IdwNLgMYbvdC3sMf-1uPnHHJUHk@z \
--to=lfdebrux@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).