You are not logged in.

#1 2014-04-11 11:14:32

Schoktra
Member
Registered: 2009-09-03
Posts: 21

[AUR] Eclipse-cpp doesn't fulfill other eclipse plugin dependencies

So after recent updates to eclipse something broke with eclipse-cdt and i was no longer able to edit my c/c++ documents in eclipse, it would launch emacs for that. I tried searching around and found suggestions to install eclipse-cpp instead and that should fix the issue. However, when I try to install it I get an error.

error: failed to prepare transaction (could not satisfy dependencies)
:: eclipse-android: requires eclipse>=3.7.2
:: eclipse-emf: requires eclipse>=3.5
:: eclipse-pydev: requires eclipse>=3.8

I've looked at the PKGBUILD and it states explicitly that the eclipse version it offers is 4.3.1 but I cannot get it to work with any of my other plugins because it doesn't offer eclipse>=3.x ? Seems kind of suspect. I'm not sure if I'm doing something wrong or if there's some issue with yaourt  causing this.

Offline

#2 2014-04-11 15:08:14

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: [AUR] Eclipse-cpp doesn't fulfill other eclipse plugin dependencies

Schoktra wrote:

I've looked at the PKGBUILD and it states explicitly that the eclipse version it offers is 4.3.1  ...

No, it doesn't, it says it that provides 'eclipse', no version given. The maintainer needs to change that to "eclipse=$pkgver".

Offline

#3 2014-04-12 12:40:43

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,401

Re: [AUR] Eclipse-cpp doesn't fulfill other eclipse plugin dependencies

Scimmia, i'm not so sure that would solve the problem (or be  a good idea for eclipse-cpp maintainer)

schoktra wrote:

I'm not sure if I'm doing something wrong or if there's some issue with yaourt  causing this.

Schoktra, whenever you got problems installing things with yaourt try installing them with makepkg to verify whether the problem is with yaourt or not.

IF makepkg gives the same error, then it's time to investigate the PKGBUILDS in question.

Very often yaourt gives errors when makepkg does not, in those cases the problem is with yaourt, not with the package.

Last edited by Lone_Wolf (2014-04-12 12:41:10)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#4 2014-04-12 15:18:54

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: [AUR] Eclipse-cpp doesn't fulfill other eclipse plugin dependencies

Lone_Wolf wrote:

Scimmia, i'm not so sure that would solve the problem (or be  a good idea for eclipse-cpp maintainer)

Why not? The problem here is straight forward; other packages have versioned dependencies, which can't be satisfied by a "provides" that doesn't have a version.

Offline

#5 2014-04-12 17:35:12

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,401

Re: [AUR] Eclipse-cpp doesn't fulfill other eclipse plugin dependencies

Scimmia, i might be wrong but i have always thought that makepkg / pacman add the real version a package has if provides doesn't specify one.
It does work that way for packages without explicit provides, and would make sense for explicit provides without a specific version.

However, man PKGBUILD suggests it works differently for explicit provides.
Looks like we need someone well versed in pacman code to clarify whether explicit provides supply the package version if none is mentioned in the provides= .


provides (array)
           An array of “virtual provisions” this package provides. This allows a package to provide dependencies other than its
           own package name. For example, the dcron package can provide cron, which allows packages to depend on cron rather
           than dcron OR fcron.

           Versioned provisions are also possible, in the name=version format. For example, dcron can provide cron=2.0 to
           satisfy the cron>=2.0 dependency of other packages. Provisions involving the > and < operators are invalid as only
           specific versions of a package may be provided.

           If the provision name appears to be a library (ends with .so), makepkg will try to find the library in the built
           package and append the correct version. Appending the version yourself disables auto detection.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB