Feature #55
automatic versioned dependencies
| Status: | New | Start date: | 06/25/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Natanael Copa |
% Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
Make the automatically generated dependencies versioned. E.g. when binary depends on .so, check the package name and version providing the binary. And make the dependency "name>=version". Alternatively the package might want to provide oldest compatible version information, so e.g. uclibc -r0 -> -r1 does not affect minimum version requirement for in rebuilds.
History
Updated by Natanael Copa over 2 years ago
I am a bit sceptic to this. What happens if package foo-1.23.4 is bad and we want roll back to foo-1.23.3? then will we need to recompile (and bump pkgrel) on all packages build after foo-1.23.4 and depends on foo. Probably not a big deal except for things like zlib and uclibc.
Actually, we could probably try strip the last digit.
dep_atleast_ver=${pkgver%.[0-9]*}
If there are no digits (like udev-143) we will end up with:
dep_atleast_ver=${pkgver}
we would probably also need some way to override it and set hard versioned dependencies.