On 6/19/05, Scott James Remnant <[EMAIL PROTECTED]> wrote: > Let's use a popular example... I make a package that > requires /usr/bin/bzgrep. > > In Debian, I would have to read the debian/changelog for bzip2 and > discover that this wasn't introduced until 1.0.1-3, and thus > Depends: bzip2 (>= 1.0.1-3) > > But in a Debian-derivative with a different release schedule (perhaps a > system used in Schools and sync'd on the start of a school year), that > might have been backported and added in 0.9.5d-3school1 > Depends: bzip2 (>= 0.9.5d-3school1) > > There's no way to express both of these relationships in the same binary > (as 1.0.1-2 would satisfy the relationship for the Debian-derivative). > > > In the RPM world, my package can simply depend on the > file /usr/bin/bzgrep existing.
What if you need a specific feature in or version of bzgrep?
