On Wed, 2008-01-16 at 09:47 +0530, Uthaiyashankar wrote: > Hi, > > This discussion happened in axis2c-dev list. Since it is a Rampart > specific issue, the discussion is moved to rampart list. > > I agree with Manjula. it is not fair to ask the user to install in a > fixed location. > > What about instructing user to install sed for windows [1], if he needs > to run the samples? we can use scripts similar to given in linux.
+1. Yes the user can choose whether to install sed for windows or to edit the files manually. > Regards, > Shankar. > > [1] http://gnuwin32.sourceforge.net/packages/sed.htm > > > Manjula Peiris wrote: > > Actually we do not put file locations relevant to Linux in Rampart > > Secpolicy files. What we do is we put the place where the secpolicy file > > should be copied relative to the AXIS2C_HOME. This is correct for both > > Linux and Windows. The problem is we can't do automatic replacement of > > AXIS2C_HOME string in Windows. > > And we initially can't do for windows because then we have to tell the > > user only to install Axis2/C on the location we are mentioning. That is > > really unfair. > > > > Thanks > > -Manjula > > > > > Senaka Fernando wrote: > > I don't think that it has been an issue beyond secpolicy AFAIK, but, I > > will try installing it in a different location to be sure about that. > > > > Option No.2 is to use another environment variable (ex:- > > %SECPOLICY_SAMPLE_HOME%) which in fact would invariably be a windows > > specific one. In the Linux build, we would rather replace this with the > > desired Linux relative (or absolute) path. This is cleaner than editing > > 13+ files and mind you around 5 places in each file. In the appropriate > > README, we will modify the way in which the user is supposed to interact. > > This is justifiable, as the user requires setting this environment > > variable only if he wants to run the samples. If he wishes not to set it, > > he simply can either edit the files or take any alternative approach. > > > > Also, you are not restricted to use paths relative to a environment > > variables in Windows. > > > > Regards, > > Senaka > > > > > >> Hi Senaka, > >> > >> Is this a problem anywhere outside secpolicy samples? > >> > >> in secpolicy samples, however, this cannot be done without sed like > >> functionality, because we need to set the paths inside certain files > >> according to the install path that is defined at the build-time. Do > >> you see any other way out of this problem? > >> > >> -Dumindu. > >> > >> On Jan 15, 2008 6:24 PM, Senaka Fernando <[EMAIL PROTECTED]> wrote: > >> > >>> Hi devs, > >>> > >>> It is a known fact that we can't use the sed command on windows unless > >>> you > >>> install an add-on. Under these circumstances we have burdened our users > >>> to > >>> do appropriate replacements so that the sed command wouldn't be > >>> necessary. > >>> The Rampart/C secpolicy set of samples is a good example. However, there > >>> is a way we could easily overcome this. > >>> > >>> We initially do things for windows and during the Linux build process we > >>> apply the sed command and covert it to Linux. This way, both Linux as > >>> well > >>> as the Windows user will have a similar experience. > >>> > >>> Regards, > >>> Senaka > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > >> > >> -- > >> Dumindu Pallewela > >> http://blog.dumindu.com > >> GPG ID: 0x9E131672 > >> > >> WSO2 | "Oxygenating the Web Service Platform" | http://wso2.com > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > >
