[solved] permanently avoid single package dependency

GordonShumway · 2018-11-14 12:49:50

Hi together,

i'm looking for a pacmanish way to avoid a single dependency for a package
coming in while still being able to upgrade that package with -Suy ?

Another user asked for this: https://bbs.archlinux.org/viewtopic.php?id=20905
but could only be worked around.

In my special case qtcreator don't crash regularly, when removing the package 'extra/qt5-quickcontrols'.
Which is one of qtcreators dependencies. (see here: https://bbs.archlinux.org/viewtopic.php?id=210622 )
But thats just what got me here.

so I did 'pacman -Rdd qt5-quickcontrols'
and now just want to avoid its automatic pulling in when upgrading with pacman -Suy,
for as long as I be happy with it.

what I figured out is:
- IgnorePkg = qt5-quickcontrol doesn't do the trick, since it pulls the recent version

- "--assume-installed qt5-quickcontrol" does what I want, but only on cmd line
(I'm not that young to not forget that option to type in all the time, all the machines I work on)

- pacman.conf has a line saying "# Misc options" !
where I tried to put "--assume-installed qt5-quickcontrol" in some variants
which gave all the same

 warning: config file /etc/pacman.conf, line 33: directive 'Assume-Installed' in section 'options' not recognized.

for example.

- an alias would probably also do the trick

but I'm curious: is there's a pacman solution I did miss?

Last edited by GordonShumway (2018-12-06 09:29:29)

arojas · 2018-11-14 19:55:20

The forum post you linked is completely irrelevant nowadays, and has nothing to do with quickcontrols. So why don't you describe what your actual issue is instead of trying to hack aroung it?

GordonShumway · 2018-11-16 13:32:13

I actually tried to make pretty clear what my issue is...

oft course, help fixing qt
would be the best solution.

my attempt here is to handle pacman
in such a case, which may return with other packages.

WorMzy · 2018-11-16 13:43:10

Sure you can, just track the qtcreator package (e.g. monitor the package update feeds), and when it updates, rebuild the package with a modified PKGBUILD in a clean chroot and add it to a custom repository that is listed above the extra repository in pacman.conf.

Of course, that's an awful lot of effort that you need to put in regularly to work around a crash that would probably be diagnosed and (potentially) fixed in a day or two if you were so inclined...

GordonShumway · 2018-12-06 09:28:11

Thank you Wormzy, I get it...

keeping it easy means keeping it fixed.
The custom repo option Is something I did not consider, yet.
have to read more about it.

Arch Linux

#1 2018-11-14 12:49:50

[solved] permanently avoid single package dependency

#2 2018-11-14 19:55:20

Re: [solved] permanently avoid single package dependency

#3 2018-11-16 13:32:13

Re: [solved] permanently avoid single package dependency

#4 2018-11-16 13:43:10

Re: [solved] permanently avoid single package dependency

#5 2018-12-06 09:28:11

Re: [solved] permanently avoid single package dependency

Board footer