On Sat, 14 Dec 2002, Andy Sy wrote: > > i've recompiled gcc 3.2 and a whole slew of other > > needed packages on mandrake 7.2, just because i > > needed to get openoffice compiling and running on > > that platform. I've invested the time and effort to > > make these packages THE RPM WAY, simply because > > when i'm all done, i can simply install the RPMs on > > any mandrake 7.2 system via a simple command. > > When RH or Mandrakesoft comes out with rpms for these > packages you've created, wouldn't it in effect make > the time and effort you spent creating these packages > redundant? That could be a lot of work spent creating > your own dependency tree that you would have to > throw away...
Not really, because i build on existing RH and MDK source RPMS. I never re-invent the wheel unless it's really necessary. Note that source rpms built for later versions will not compile as is for old mdk versions, some mods are needed. > Under Slackware, you spend very little time and effort > creating a package so there isn't much to regret. Nor > is the requirement to move to an official version of > the package as urgent as would be on Redhat or Mandrake > one. Bottomline is that you get a lot of flexibility > if you don't have to worry about official dependencies. > You're in control. I actually find their absence to be > to be superior, covenience-wise. With open source you are always in control. Whether with slack or with RH or MDK. Dependencies are controlled by the ./configure statement in the SPEC file. _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
