Re: Forcing a package to get installed

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

 



On 8/30/05, John Summerfied <debian@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> Manilal K M wrote:
> > On 8/30/05, John Summerfied <debian@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> >
> >>James_Martin@xxxxxxxxxxxxxxx wrote:
> >>
> >>>Sure.. you could have the %pre section of your RPM remove
> >>>/usr/lib/iiim/le/unitle/MALAYALAM/data/inscript.data.. Have your package
> >>>contain  /usr/lib/iiim/le/unitle/MALAYALAM/data/inscript.data.custom, and
> >>
> >>Removing the file doesn't do anything useful
> >>
> >>
> >>>the %post section would copy
> >>>/usr/lib/iiim/le/unitle/MALAYALAM/data/inscript.data.custom to
> >>>/usr/lib/iiim/le/unitle/MALAYALAM/data/inscript.data.
> >>
> >>Removing or updating iiimf-le-unit after this would be harmful. _I_
> >>would look to removing the package causing the conflict, or merging the
> >>two costomising one to provide both functionalities.
> >>
> >>It might also be worth reporting a RFE bug for iiimf-le-unit, describing
> >>what you want to achieve.
> >>
> >>>James S. Martin, RHCE
> >>>Contractor
> >>>Administrative Office of the United States Courts
> >>>Washington, DC
> >>>(202) 502-2394
> >>>
> >>>anaconda-devel-list-bounces@xxxxxxxxxx wrote on 08/29/2005 03:00:22 AM:
> >>>
> >>>
> >>>
> >>>>Hello all,
> >>>>I have built an rpm (nila-kbd) for incorporating malayalam keyboard
> >>>>layout in FC-4. But this package has a conflict with the file
> >>>>/usr/lib/iiim/le/unitle/MALAYALAM/data/inscript.data which belongs to
> >>>>another package(iiimf-le-unit). So when I tried to install it using
> >>>>rpm it give some conflict errors. If I use --force it will work, it
> >>>>will get installed.
> >>>>My actual pronlem is I have to integrate this package into anaconda,
> >>>>then how can I force this package to get installed through anaconda
> >>>>any thoughts ??
> >>>>
> >>>>regards
> >>>>Manilal
> >>>>
> >>>>_______________________________________________
> >>>>Anaconda-devel-list mailing list
> >>>>Anaconda-devel-list@xxxxxxxxxx
> >>>>https://www.redhat.com/mailman/listinfo/anaconda-devel-list
> >>>
> >>>
> >>>_______________________________________________
> >>>Anaconda-devel-list mailing list
> >>>Anaconda-devel-list@xxxxxxxxxx
> >>>https://www.redhat.com/mailman/listinfo/anaconda-devel-list
> >>>
> >>
> >>
> >>--
> >>
> >>Cheers
> >>John
> >>
> >>-- spambait
> >>1aaaaaaa@xxxxxxxxxxxxxxxxxxxxxxx  Z1aaaaaaa@xxxxxxxxxxxxxxxxxxxxxxx
> >>Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
> >>
> >>do not reply off-list
> >>
> >>_______________________________________________
> >>Anaconda-devel-list mailing list
> >>Anaconda-devel-list@xxxxxxxxxx
> >>https://www.redhat.com/mailman/listinfo/anaconda-devel-list
> >>
> >
> >
> > Thanks everyone.
> > The suggestion from James_Martin@xxxxxxxxxxxxxxx worked for me. I hope
> > now everything will work fine The %pre, %install and %post sections of
> > the SPEC file is as follows:
> >
> > %pre fc3
> > if [ -f /usr/lib/iiim/le/unitle/MALAYALAM/data/inscript.data ]
> > then
> >     rm -f /usr/lib/iiim/le/unitle/MALAYALAM/data/inscript.data
> > fi
> > if [ -f /usr/lib/iiim/le/unitle/sysime.cfg ]
> > then
> >
> 
> Please reread my reply. This relies on the order packages are installed
> and will break when RH issues an update because your file will be
> replaced. It will fail if, for whatever reason, you remove Red Hat's
> package, because your file will be removed.
> 
> It also means RPM will show the package is damaged when you "rpm -V" it.
> 
> What you are doing is not "The Righr Thing."
> 
> 
> --
> 
> Cheers
> John
> 
> -- spambait
> 1aaaaaaa@xxxxxxxxxxxxxxxxxxxxxxx  Z1aaaaaaa@xxxxxxxxxxxxxxxxxxxxxxx
> Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
> 
> do not reply off-list
> 
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list
> 

I know I am not doing the right thing, but this package change is
relevant only for  a distribution that I have customized. For other
distros and future releases, I am planning to make another RPM. So for
the community, I don't think there will be any issues
regards
Manilal


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux