On 05/26/18 02:34, Chase wrote:
Whichever solution is easier to maintain and build for you guys, as long as it
works in full, if it doesn't I'll be sure to let you know. By the way, do you
want to do the Minix port or should I? I was just going to copy paste a lot of
the NetBSD files and rename them to minix and test from there since they share
the same userland, but I think you are probably way more of an expert in this
field than I.
No sorry, I'm afraid I don't have enough time to start a new port.
Although it would be interesting. I've already worked with Minix by the
end of the 80s.
And I've learned the details of UNIX kernel from the fantastic book of
Andrew Tanenbaum.
But see my first sentence ...
Best Regards, Ulrich
Thank you for your time,
-Chase
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On May 25, 2018 7:24 PM, Ulrich Wilkens <m...@uwilkens.de> 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.
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.
Best Regards, Ulrich
CDE will not be runnable in this directory however, but this should be
suitable for packaging.
-jon
On 05/24/2018 06:19 PM, Chase via cdesktopenv-devel wrote:
Hi all,
If any of you were curious about the status of the debian package, I
must unfortunately report that development has temporarily halted. It
isn't that I have lost interest or anything, the problem is that, in
short, debian needs to be able to install the package to customizable
directories, and the install script only supports installation on
root. So if anyone wants to see a debian package come to fruition, see
if you can make this change, and I will get right back to work on it,
in the meantime, I will be doing code cleanup and starting a Minix port.
Thank you for your time,
-Chase
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
--
Ulrich Wilkens
Email: m...@uwilkens.de
-------------------------------------------
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
--
Ulrich Wilkens
Email: m...@uwilkens.de
------------------------------------------------------------------------------
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
