On 05/25/2018 06:24 PM, Ulrich Wilkens wrote:
On 05/25/18 02:25, Jon Trulson wrote:
I will have some time to look at this next week. I think I should be
able to persuade installCDE to install it's files in a different
directory/$DESTDIR.
By mid of last year I already worked on a solution for the fixed install
paths. I used 3 macros that already existed in CDE:
CDE_INSTALLATION_TOP, CDE_CONFIGURATION_TOP and CDE_LOGFILES_TOP.
Their default values are /usr/dt, /etc/dt and /var/dt.
You can change them if you give additional options to make World, e.g.
make CDE_INSTALLATION_TOP=/usr/local/dt
CDE_CONFIGURATION_TOP=/usr/local/etc/dt World
If you leave out some of the options the default values are used.
After this everything in CDE is built with the new paths:
binaries, libraries, config files, log files, database files and
installation scripts.
The exception is the documentation (manual pages, help files and
dtinfo files). This is not done so far. And I'm not even sure whether
it should be done. What is better? Having the same documentation
on all installations or having a documentation which matches the
current installation?
But anyway, documentation would be another big task. A lot of text
files must go through some sort of macro parser.
What do you think about this? Is it a suitable solution for Linux
packages?
I did it for my port of macOS, where it is not allowed to install
to /usr or /etc if SIP is enabled, not even as root.
Yes, but the CDE_INSTALLATION_* defines serve a different purpose than
what I am doing in the installer for packaging...
All that's needed in the installer (with -destdir) is that everything is
installed in a "cde-sysroot", with all of the permissions, ownership,
and the like preserved. It does not (and usually cannot) actually be
run in that location -- it's purely an artifact used for building a package.
The CDE_INSTALLATION_* defines specify to everything at runtime where
these directories actually are, so the software can find things. So it
serves a totally different purpose.
But please keep in mind that my changes would need to be merged with
all the patches from this year and this would need some time.
And as always it would need intensive testing.
Well, lets take the time then. As I mentioned earlier, there is no
"deadline" to make a release, but lets at least get one out this year :)
-jon
[...]
--
Jon Trulson
"But when I'm in command, every mission's a suicide mission."
- Zapp Brannigan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
