Here's another question -- how about deleting the contents of tmp/ (this includes files like the pre-oscar.rpmlist, CLI logs, etc.) during %postun? This way when the user executes the start_over script, the oscar-base* RPMs are uninstalled along with the entire /opt/oscar directory.
Also, should we include /var/log/oscar as part of the oscar-base RPM package? Cheers, Bernard On 11/29/07, Bernard Li <[EMAIL PROTECTED]> wrote: > Hi Geoffroy: > > On 11/29/07, Geoffroy Vallee <[EMAIL PROTECTED]> wrote: > > > > Regarding the naming conventions between RPM and Debian packages -- I > > > would vote to have them as consistent as possible. It makes it easier > > > for users and developers alike to figure things out. > > > > If a discussion starts about that, i will be happy to participate. :-) > > Well that was my $0.02 -- I welcome others to voice their opinions. > > > > P.S. For RPM packaging, I plan to set $OSCAR_HOME = /opt/oscar (or > > > %basedir) after the oscar-base RPM is installed (%postinstall) -- > > > since if you are installing via binary packages, the path is set so > > > might as well set it up after the package installation for the user > > > automatically... > > > > Just a remark FYI and give you an idea of what i did and where i go for > > Debian stuff: what you propose is kind of forbidden on Debian (for what > > i understand), it is prohibited to use environment variables to make a > > software work; you have to use a configuration file or directly install > > the software on the system. Currently, i assume that all binaries, > > libraries and so on should be installed directly into the system. > > Actually, i already have few patches to do so; which are automatically > > applied when one creates Debian packages. This is still incomplete and i > > do not think i will have the time to work on that before few weeks or > > even months since i want to finish first OPM and the new GUI (which will > > use OPM). I guess with that you have a pretty good idea for the current > > situation for Debian, let me know if you want more details. > > Okay let me explain the situation. I believe install_cluster sets up > the environment variables ($OSCAR_HOME) correctly to begin with, > however, the issue is that let's say I install the RPM, and then > decided to run start_over, the script will bail because $OSCAR_HOME is > not set (because I didn't run install_cluster). > > That's why I wanted this environment variable to be set right after > oscar-base RPM is installed (%post), since the %basedir is static > anyways and I see no harm in setting it. > > But if you say this is forbidden in Debian, well, I guess we need to > look for another solution then. > > Cheers, > > Bernard > ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
