On Fri, Mar 12, 1999 at 04:58:26PM +0100, Santiago Vila wrote: > > > > > It is technically possible to make package A to conflict with > > > > > releases of > > > > > B earlier than "p" and also with all releases of B between "r" and "s" > > > > > but not with release "q" of B (where p < q < r < s)? > > > > > > > > AFAIK, dpkg can't even do 'all releases between r and s' without naming > > > > each one individually. > > > > > > So: may it be done? (by naming them individually or whatever). > > > > It may be done (at the expense of a possible hideously long Conflicts: > > line) if you list every single conflicting version, I believe. > > How well does dpkg manage long Conflicts lines? > In which case could this be a problem? > > Would it be acceptable if s - r + 1 = 5, for example?
Every new conflict, dependency, etc., requires a new structure, and the more complex they are, the more complex it is for dpkg to check the interelations (so yes it slows it down obviously). I just have a question, what is it you are trying to do and for what reasons? This information might help a little more. -- ----- -- - -------- --------- ---- ------- ----- - - --- -------- Ben Collins <[EMAIL PROTECTED]> Debian GNU/Linux OpenLDAP Core - [EMAIL PROTECTED] [EMAIL PROTECTED] UnixGroup Admin - Jordan Systems The Choice of the GNU Generation ------ -- ----- - - ------- ------- -- ---- - -------- - --- ---- - --
