The whole day today, I have been trying to convince management that perhaps having everything under one package based enviromnent (read OpenPkg) is a good idea, and that it is not earth shattering to move paths around.
The biggest concern I came up against was : 1) How do you know OpenPkg will be around next year ? 2) How will the upgrades to the next version of OpenPkg work ? Both valid concerns. Its hard to tell to convince managers that to make open source work you have to contribute to it ...at least by using it and testing it and validating it. I am sure people here have faced these questions before... Can you suggest how I should tackle them ? Thanks again, -ansh > -----Original Message----- > From: Ralf S. Engelschall [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 05, 2003 10:37 AM > To: [EMAIL PROTECTED] > Subject: Re: FW: Trying to understand openpkg installroot > > > On Wed, Nov 05, 2003, Anshuman Kanwar wrote: > > > Thanks for your detailed reply. Very helpful. > > > > What if I build openpkg with : > > > > $ sh openpkg-***-***.src.sh --prefix=/ --user=here --group=here > > > > Will that break anything ? > > Yes, it _will_ break your system -- perhaps not in this steps, but at > least after you installed a few packages containing files similar to > what the system already has! Please don't do this until you > really want > to create a dedicated "OpenPKG OS" ;-) > > > Though I appreciate the ability to run multiple instances > of an app on one > > box, (This is one thing sadly missing in any other > packaging system ... and > > I've researched quite a few) my problem is that we run an > ASP environment > > and changing application paths at this point is just not an option. > > For customers at C&W which insist on particular paths we usually solve > the problem by just creating a few legacy symbolic links inside the > system area pointing to the OpenPKG area. Usually you don't need very > much legacy paths as experience shows. It is usually just about half a > dozend or so... > > > As far as deployment is concerned, I currently use an > overly infrastructure > > over ssh/scp to manage applications using push. I have a > good mind to move > > to using cfengine, but there are some timing issues we > faced while testing > > that. > > You should be able to integrate OpenPKG into this scheme without > problems, I think. > Ralf S. Engelschall > [EMAIL PROTECTED] > www.engelschall.com > > ______________________________________________________________________ > The OpenPKG Project www.openpkg.org > User Communication List [EMAIL PROTECTED] > ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
