Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1991 - xinetd requires gcc version

Attached to Project: Arch Linux
Opened by clint webb (cjdj) - Friday, 07 January 2005, 14:22 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

current xinetd version fails if installed version of gcc is 3.3.3-1.

xinetd states that it cant find libstdc++.so.6

Upgrading to current version of gcc fixes the problem, but a version dependancy would be nice.

This task depends upon

Closed by  Judd Vinet (judd)
Friday, 07 January 2005, 21:21 GMT
Reason for closing:  Won't fix
Comment by Judd Vinet (judd) - Friday, 07 January 2005, 20:00 GMT
You will find this happens with many packages in Arch. We do not include version-specific dependency information unless there is a special need to support more than one version of a package.

Support-wise, we assume that you are following the Current tree and are up-to-date with pacman -Syu. Once you start mixing up package versions, missing-library errors could pop up.

It's a trade-off, I know. But more stringent dependencies can also mean much more work when a package like gcc or readline is upgraded. If we had bound the dependency to gcc=3.4.3, then all dependent PKGBUILDs would need to be updated when a new gcc released. But if we bound the dependency to gcc>=3.4.3, then that too may be an incorrect assumption if the library SONAME changes in a future version.

Loading...