[pacman-dev] [PATCH 0/1] Introduce "AssumeInstalled" option in the config file

[Eli Schwartz]

On 9/5/20 3:11 AM, Damjan Georgievski wrote:
> On Fri, 4 Sep 2020 at 03:35, Andrew Gregory <andrew.gregory.8 at gmail.com> wrote:
>> Without a better use case, I'm -1 on this.  --assume-installed was
>> intended for ignoring individual dependencies in exceptional
>> circumstances, not permanently ignore a dependency you don't like.
>> The preferred way of dealing with that, should you feel the need, is
>> with a meta package.
> 
> and how do I plug that into pacstrap? custom repo? that seems like a
> much bigger overkill :/

Do you need to install it during pacstrap itself to override packages in
the base install? If not, you can simply execute pacstrap && pacman -r
/mnt -U /path/to/metapackage.

About a year ago, I added a -U option to pacstrap, which makes it use
pacman -U for all packages; you may therefore pipe a list of packages to
install as such:

mkdir ./fakedb
{ pacman --dbpath ./fakedb -Syp base; echo /path/to/metapackage; } |
    pacstrap -U /mnt -

Since pacstrap may be repeatedly run on the same existing root and does
not require that it be the one to create said root, you may also do this
much simpler form (assuming the metapackage does not have dependencies,
which it presumably shouldn't):

pacstrap -U /mnt /path/to/metapackage
pacstrap /mnt [base otherpackages]


Either way, I'm even less convinced of the need for a pacman.conf option
if the only time it is needed is during pacstrap and never again; even
if it were true that you needed it then, I'd argue you could just as
well install as normal, then replace the package you didn't want with a
metapackage after chrooting in.

-- 
Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1601 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/pacman-dev/attachments/20200905/d3dfc7d9/attachment.sig>