Subj : MBSE, Sysops and distros
To   : RJ Clay
From : Vince Coen
Date : Sun Aug 16 2015 02:47 pm

Hello RJ!

Saturday August 15 2015 13:46, you wrote to mark lewis:

> Hi mark!

> 12 Aug 15 23:02, you wrote to me:

ml>> 12 Aug 15 19:19, you wrote to Vince Coen:

VC>>>> If you look at my changes for 1.0.4,

RC>>> IIRC;  I wanted to, in order to see how you were doing it, but
RC>>> don't think I ever actually had anthing for it (or if I did, I
RC>>> can't find it now). And I don't see the changes in the Hg
RC>>> repository, though all I have is the 'default' branch...

ml>> grab the repo and revert back to before andrew's changes and you
ml>> should be able to save the files out to another directory where
ml>> you can checkout the latest again and then run a diff on them to
ml>> pull out the real changes you seek... that or maybe there's a way
ml>> to have the repo do that for you? i dunno... i always tend to do
ml>> it manually by reverting and copying out, then coming back to the
ml>> present and doing a diff between the reverted and the now code...

>   The commits need to be there in order to 'revert' to them, and
> they're not;  at least not in the repo checkout ("clone") that I have.
> I'll just need to get with them (Andrew and Vince) about it.


ml>> the main thing, as i see it, is that there should be an option
ml>> presented, whether from a local build or from a package as to
ml>> where to install to...

>   True.


ml>>  i always hate it when i install something via apt that i
ml>> want only for my personal user but it gets put in place for all
ml>> users...

>   In general, a distros' package manager is for installing things for
> system wide use, not just a particular user...


Have now installed 106 over the installed 104 still using /home instead of
/opt.

Compiling the build was simple  just used

./configure --prefix=/home/mbse

then used the standard su, make install  job done.


We counld update mbsetup to check if the install is NOT to the standard /opt
and if so migrate the existing file and msg .data files to use the new path.
That will remove 98% of any migration.

The oonly other areas to look at are:

1.  Check all scripts in ~/etc that the full path is not hard coded but using
$MBSE_ROOT as originally supplied

2.  If not using the .profile export of $HOME in crontab to pre-set the paths
i.e.,

#Hourly
00 0-23 * * * $MBSE_ROOT/etc/hourly


then modify the "/opt" to "/home".

Now migration is complete.



Vince

--- Mageia Linux v4/Mbse v1.0.4/GoldED+/LNX 1.1.5-b20130910
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)