Re: Overriding automatic dependancies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 11 Feb 2004, Tim Mooney wrote:

> In regard to: Overriding automatic dependancies, Matt Pounsett said (at...:
> 
> >I'm trying to build an RPM from some perl code which 'require's some different
> >perl modules depending on the system architecture (Win32 vs. *nix).
> >Unfortunately, rpmbuild's automatic dependancy checking is determining that
> >the RPM depends on the Win32 modules, which are not present on unix systems.
> >Is there a way that I can override that one dependancy, without having to turn
> >off all automatic dependancy checking?
> 
> Wow, this is almost verbatim of a question that was asked on the list
> a couple weeks ago.  Did you check the archives for the list to see what
> the responses were?
> 
> There is no such thing as "NoRequires: perl(Some::Win32:Module)", but
> what some people apparently do is just add
>
Jeff, 

How hard would it be to do something like a NoRequires (I don't 
particularly like that name but for the sake of argument it will do).  
Really what something like this would do is give hints to  the 
autodependency stuff to ignore particular found depencencies but not turn 
off autodependency stuff alltogether?  I have been happy with the 
hack for my non-public distro, but I understand the desire to go 
beyond a hack provided it would not utterly complicate things.
   
Cheers...james


_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux