On 06/20/2018 06:01 PM, Chase wrote:
I say that if we are going to push out one last release before the transition,
make it 2.2.5, and then the autotools release can be 2.3. Can we also reenable
the font editor and try to debug it after 2.2.5? If it's only problem is
renamed x11 headers and compiler warnings, that is a relatively easy fix.
The next release will be 2.3, because things.
Autotools will take a while, before it's functional. There are many
steps to building CDE, it will not be a trivial task to replicate in
autotools.
As for dtudc*, why? Who needs it?
If you really want it, there is no reason it could not just be
maintained outside of CDE as a separate project -- just requiring a
X11/Motif/CDE dev environment to build.
Besides, there are far better font editors out there, if that's your thing.
TBH, I'd like to get rid of dtmail as well, unless someone wants to
drag it into the 21st century.
Would switching to autotools also solve the rpath problem?
Possibly, as I understand libtool changed it's behavior WRT to rpath.
In CDE for linux, rpath is added via ExtraLoadFlags in
config/cf/lnxLib.rules. You could probably just override that in
hosts.def yourself and see what happens.
According to https://wiki.debian.org/RpathIssue, there is this paragraph
which would seem to apply to CDE:
"While there's no policy dictating the accepted use of RPATH, it's been
a general consensus that RPATH use is discouraged, given the
interactions between the above reasons and Debian's way of dealing with
libraries and package dependencies.
Currently, the only generally accepted use of this feature in Debian is
to add non-standard library path (like /usr/lib/<package>) to libraries
that are only intended to be used by the executables or other libraries
within the same source package. "
So... not a big deal it would appear..?
-jon
Thank you for your time,
-Chase
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On June 20, 2018 12:04 PM, Jon Trulson <j...@radscan.com> wrote:
On 06/19/2018 09:33 PM, Chase via cdesktopenv-devel wrote:
Hi all,
Matthew T. and I have had a conversation about imake and whether or not
it would be a good idea to merge with master or not. After doing a bit
of discussion, I sent a message to alan coopersmith to see if anyone at
the imake team would be willing to look at our code and help us merge,
to which he revealed to me that there is no imake team, and there hasn't
been one since 2014, and it is very unlikely that anyone else will pick
up the project (he even went as far as to consider appointing me as the
maintainer of imake). So if it wasn't official already, it is now, we
are maintaining both imake and CDE.
Congratulations! :)
I briefly considered moving to
meson, however Matthew informed me that this would severely limit
compatibility with legacy operating systems, and it looks like Cmake has
that same problem. So the way I see it, we have two options going
forward, we either move towards the gnu autotools, or we merge with
master and continue from where they left off on our own. I was
considering posting some patches that would sync us with upstream a bit,
but I don't know how much they would be worth with this news (one of
them enabling cross compiling).
How should we continue from here? Thoughts?
Imake is dead, and I see no point in trying to "take over" and improve
it. Autotools (as others have also mentioned in this thread) is the way
to go moving forward. We might be able to leverage some of the work X11
did there as well.
With autotools, we could get multi-core builds, cross compiler support,
build-time detection of system features, languages, and capabilities,
and much more. We could take advantage of their finer grained
installation support (--bindir=DIR, --libexecdir=DIR, --runstatedir=DIR,
and a dozen others to also resolve the whole "stuff everything into
/usr/dt" issue as well.
We should (as X11 and Motif did) develop it along side Imake until it is
working well enough to just toss out Imake. We would also get "make
install" working (though this does not have to wait for autotools
integration), and we could eventually get rid of the UDB databases and
their dependencies too.
So, I am all for it. A question though, is timing. Should we get a
stable release out first, and then start working on something like this?
Alternatively, we could just keep releasing occasional development
releases until we are ready, but that would mean a stable release might
still be a long way off.
[...]
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Jon Trulson
"Fire all weapons and open a hailing frequency for my victory yodle."
- 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
--
Jon Trulson
"Fire all weapons and open a hailing frequency for my victory yodle."
- 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
