On 10/10/23 07:00, Erich Eckner wrote:
Hi,
...
This is (one possibility for) the second option, that I mentioned, which
I was afraid might break a lot of stuff on my machines :-/
I meant put it in /usr/local/xxx/ not directly in /usr/local.
Or in /opt/xxx/
I see, that the root cause (and
Hi,
sry for leaving out the details in the first place. I'll put them in-line:
On Tue, 10 Oct 2023, Christian Heusel wrote:
On 23/10/10 05:28AM, Genes Lists wrote:
On 10/10/23 02:41, Erich Eckner wrote:
I have two packages, A and B, which both provide the same file X.
...
One possibility i
On 23/10/10 05:28AM, Genes Lists wrote:
> On 10/10/23 02:41, Erich Eckner wrote:
> >
> > I have two packages, A and B, which both provide the same file X.
> ...
> One possibility is to simply change the unofficial one to install in
> /usr/local (all of it /usr/local/etc, /usr/local/bin, /usr/local
On 10/10/23 02:41, Erich Eckner wrote:
Hi fellow-archers,
Hi!
I have two packages, A and B, which both provide the same file X.
...
Without knowing more its a bit hard to say.
For example are A and B actually the same application but different
versions (git vs stable). If so, then just
Hi fellow-archers,
I have two packages, A and B, which both provide the same file X. Is there
a way to tell pacman to ignore file X in package B, so it is installed
(and updated) solely with A? My current ideas are:
* repackage B (the official package), so it does not include X anymore ->
te