Arch Linux

funkyou

Member

From: Berlin, DE

Registered: 2006-03-19

Posts: 848

Website

[solved] conflicts, provides & package upgrade

Some small questions...

I am currently investigating a bit around in making separate KDE
packages because i do not use most of the applications. But i want to do
it not the  obvious way of splitting everything into a separate pkg, as KDE
is still main DE. I think more of the kde standard packages, stripped down
to the most needed, and providing the rest of the package in a modular
form. This would make the whole thing easier to maintain for me, if i
ever need an app i have removed from the original packages. So i would
have kdepim installed for example, but there would only kmail and
korganizer be included, and the rest of it like kontact and knode and so
on will be in separate packages.

Now to my questions... Maybe i want to build the package kdepim and
inside the PKGBUILD it looks like this:

pkgname=kdepim-light
...
groups=('kde-light')
provides=('kdepim')
conflicts=('kdepim')
depends=('kdelibs-light>=3.5.3' 'kdebase-light>=3.5.3' 'gpgme' 'libmal' 'cyrus-sasl' 'libxss')
...
and so on...

As you can see, i have added conflicts and provides to the PKGBUILD.
provides, because i want it to be compatible with other arch packages
which may depend on the original package (i just do not want to rebuild
every kde app like amarok, but just use the repos), and conflicts
because it will be installed to the same location as the original KDE. So...

What happens if i do pacman -Suy? Will kdepim-light be overwritten by
the standard arch package from extra when there is a newer version
available? (maybe because of the provides=('kdepim'))

And what if i provide a newer version of kdepim-light? will the old version
be upgraded, or will it conflict with itself because of the conflicts and
provides directives?

Well, you may say "what a stupid question" or  "try it yourself, buddy"
But my machine takes ages to build KDE, so i want to be sure before i
start to build it by issuing my ultra-cheap build-all.sh script and let it
run over night...

---

want a modular and tweaked KDE for arch? try kdemod

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: [solved] conflicts, provides & package upgrade

Will kdepim-light be overwritten by
the standard arch package from extra when there is a newer version
available?

No. Pacman now sees two separate packages, kdepim and kdepim-light. The conflicts= directive in kdepim-light ensures that the two packages cannot be installed at the same time, so if you have the light version installed, pacman won't do anything with the standard version.

will the old version be upgraded, or will it conflict with itself because of the conflicts and provides directives?

It will be upgraded. As mentioned, these are two different packages, with a conflict between them. I expect a package might conflict with itself if pkgname= and conflicts= are the same - I've never tried it, though.

funkyou

Member

From: Berlin, DE

Registered: 2006-03-19

Posts: 848

Website

Re: [solved] conflicts, provides & package upgrade

Thx for your reply.

I will just try it with these settings, lets see what happens

-EDIT- It works like a charm No conflicts with the standard KDE
packages, no problem to upgrade the customized packages, and no
problem to install KDE apps from the repos...

I just love pacman

---

want a modular and tweaked KDE for arch? try kdemod