I don't want to turn this into a holy war but I would much rather have the flexibility and feature set to at least understand what a dependency is. And given that you can either do them auto or manual, and inside of that specify less than greater than or equal to a certain version I don't see how it's so bad. I'll take yum -yi crazy_package_with_15_deps over the try install grab another try install grab another dance any day. Using Slackware packages is like going back in time 5 years. If you take the time and #1 read the docs on rpm and #2 put some thought into your package layout you can end up with something that works really well. There are some really crappy packages out there but unfortunately rpm can't really protect you from those... The features I take advantage of in RPM on a daily basis in my "day job" save me days a year of maintenance nightmares. Tracking changed config files automatically and not replacing them, seamless upgrades with post-implementation scripts to do any clean-up or service restarts, easy separation of package contents into sub packages, build-prereqs, prereqs, dependancies and yum. On 10/22/06, Yossi Neiman <iaxteling@cartissolutions.com> wrote:
And this is why I am a Slackware / Slamd64 masochist... I actually think it's a lot less masochistic than having to muck around with rpms and such. *grin*
Yossi Neiman Cartis Solutions, Inc. - http://www.cartissolutions.com
Paul Tinsley wrote:
Well the easiest fix for this specific problem is to not adversise those abilities from the rpm, rpm figures those out automagically using ldd on every executable in an rpm file list, you can easily turn that off by adding this to your spec file:
AutoReqProv: no
Then you just need to build the appropriate Provides: line in the spec file for what it does provide, freeswitch.
On 10/21/06, * Peter Nixon* <listuser@peternixon.net <mailto:listuser@peternixon.net>> wrote:
Matt
I am aware that it has been discussed previously. I am aware that some of the libs have extra patches, and I am happy to build packages for them also that include the patches. I DO have freeswitch built in rpm form. (See for example
http://software.opensuse.org/download/server:/telephony/SUSE_Factory/x86_64/...
<
http://software.opensuse.org/download/server:/telephony/SUSE_Factory/x86_64/...
)
The problem is what the FREESWITCH rpm does to the rest of the system when you have it available in a repository.
Take for example the error messages I posted. They state that when someone tries to install "grep" on their system (assuming that they dont have it) rpm considers freeswitch-snapshot as a possible providor of "pcre". Likewise if they want to install something that relies on spandsp or sqlite it will try to install freeswitch to satify the dependency..
Do you see the problem?
-Peter
On Sat 21 Oct 2006 13:26, Matt Klein wrote: > Peter, > This has been discussed. Issues on current are, some of the.. > necessary code additions/modifications to the libs may or may not ever be > available in your external libs. > > Please advise on how you suggest we proceed. > > Are you exporting LD_LIBRARY_PATH to /usr/local/freeswitch/lib prior? > > thx > -m > > On Sat, 21 Oct 2006, Peter Nixon wrote: > > Hi Guys > > > > Here is the result of building a freeswitch package with all of its > > dependencies inline. It confuses the hell out of rpm when you go an try > > to build OTHER packages that rely on those dependencies which are already > > provided by standard packages: > > > > Fedora_Extras_5 i586 expansion error > > have choice for libpcre.so.0 needed by grep: freeswitch-snapshot pcre > > have choice for libsqlite3.so.0 needed by rpm-libs: freeswitch-snapshot > > sqlite have choice for libsqlite3.so.0 needed by rpm: freeswitch-snapshot > > sqlite have choice for libsqlite3.so.0 needed by rpm-build: > > freeswitch-snapshot sqlite > > > > Now, I CAN work around this by manually specifying preferences for each > > of these packages in ALL of my other builds but this is really bad karma > > and requires me to screw around with almost 50 other packages just to > > have the pleasure of building freeswitch. ick.. > > > > Please please fix the build so that it will use external libs if they are > > available. I will happily package any external libs that are required > > (infact I already have done so) and can apply patches to any that need > > them. > > > > Cheers > > -- > > > > Peter Nixon > > http://www.peternixon.net/ > > PGP Key: http://www.peternixon.net/public.asc <http://www.peternixon.net/public.asc> > > _______________________________________________ > Freeswitch-dev mailing list > Freeswitch-dev@lists.freeswitch.org <mailto:Freeswitch-dev@lists.freeswitch.org> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev > UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-dev > http://www.freeswitch.org
--
Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org <mailto:Freeswitch-dev@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
------------------------------------------------------------------------
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org