hi,

"simbad" <Han### [at] gmxde> wrote:
> I worked on the slackware-14.x support and got an executable. But its not good
> enough to let it out into the wild.

:-)

> But it builds with Qt4 and even the OpenGL things seems to work. But docking of
> the widgets and some file-loading things are not ready.

thanks.  keep "us" in the loop, please.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > I worked on the slackware-14.x support and got an executable. But its not good
> > enough to let it out into the wild.
>
> :-)
>
> > But it builds with Qt4 and even the OpenGL things seems to work. But docking of
> > the widgets and some file-loading things are not ready.
>
> thanks.  keep "us" in the loop, please.
>
>
> regards, jr.

Ok.
I do have a version that seems to run on slackware 14.1 and 14.2
As I am not very familiar with the functionalities of povmodeler and the qt
library tweaks it may still have bugs.

But it looks promising as it has been build against the distros qt libs
versions. So Qt4.x

Next would be to pack that and make it available. But this comes the next days.
For now I check whether the other packages still build and work.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > thanks.  keep "us" in the loop, please.
>
> Ok.
> I do have a version that seems to run on slackware 14.1 and 14.2
> As I am not very familiar with the functionalities of povmodeler and the qt
> library tweaks it may still have bugs.
>
> But it looks promising as it has been build against the distros qt libs
> versions. So Qt4.x
>
> Next would be to pack that and make it available. But this comes the next days.
> For now I check whether the other packages still build and work.

have a look at: <https://slackbuilds.org/>
that is sort of the standard.

if you want to discuss stuff, feel free to email direct.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > "jr" <cre### [at] gmailcom> wrote:
> > > thanks.  keep "us" in the loop, please.
> >
> > Ok.
> > I do have a version that seems to run on slackware 14.1 and 14.2
> > As I am not very familiar with the functionalities of povmodeler and the qt
> > library tweaks it may still have bugs.
> >
> > But it looks promising as it has been build against the distros qt libs
> > versions. So Qt4.x
> >
> > Next would be to pack that and make it available. But this comes the next days.
> > For now I check whether the other packages still build and work.
>
> have a look at: <https://slackbuilds.org/>
> that is sort of the standard.
>
> if you want to discuss stuff, feel free to email direct.
>
>
> regards, jr.
Hi ho,
there are two packages available.

 * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-1hjl.tgz
 * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-2hjl.tgz

for slackware-14.1 and slackware-14.2

I experienced segfaults on first start. I could not find the cause for now.
While it has vanished with the next start it has been hard to identify.

While checking a coredump I found an iterator through the action list failed.
But the debugging on slackware is hard, as the X11 in a vm runs without any
accelleration support. Everything is very slow.

So look out for those crashes. Maybe I got some more ideas about the situation
that will cause this.

I did not created any slackbuild-script but added the slack-desc file to the
repo. As it should be easy to be build on a slackware distro now I think I will
not deliver the slack-build script.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> Hi ho,
> there are two packages available.
>
>  * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-1hjl.tgz
>  * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-2hjl.tgz
>
> for slackware-14.1 and slackware-14.2
>
> I experienced segfaults on first start. I could not find the cause for now.
> While it has vanished with the next start it has been hard to identify.
>
> While checking a coredump I found an iterator through the action list failed.
> But the debugging on slackware is hard, as the X11 in a vm runs without any
> accelleration support. Everything is very slow.
>
> So look out for those crashes. Maybe I got some more ideas about the situation
> that will cause this.
>
> I did not created any slackbuild-script but added the slack-desc file to the
> repo. As it should be easy to be build on a slackware distro now I think I will
> not deliver the slack-build script.

ah, thanks.  no idea whether it will be "easy to build" since all you provide is
a binary (system) install.  (I was minded to try the software, but would want to
build and install it to "fit in")  cheers, anyway.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > Hi ho,
> > there are two packages available.
> >
> >  * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-1hjl.tgz
> >  * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-2hjl.tgz
> >
> > for slackware-14.1 and slackware-14.2
> >
> > I experienced segfaults on first start. I could not find the cause for now.
> > While it has vanished with the next start it has been hard to identify.
> >
> > While checking a coredump I found an iterator through the action list failed.
> > But the debugging on slackware is hard, as the X11 in a vm runs without any
> > accelleration support. Everything is very slow.
> >
> > So look out for those crashes. Maybe I got some more ideas about the situation
> > that will cause this.
> >
> > I did not created any slackbuild-script but added the slack-desc file to the
> > repo. As it should be easy to be build on a slackware distro now I think I will
> > not deliver the slack-build script.
>
> ah, thanks.  no idea whether it will be "easy to build" since all you provide is
> a binary (system) install.  (I was minded to try the software, but would want to
> build and install it to "fit in")  cheers, anyway.
>
>
> regards, jr.

git clone https://github.com/tribad/povmodeler.git
cd povmodeler
git checkout slackware14.x
cmake .
make
make install

A build script will not do anything different. So if you have anything different
than the standard slackware 14 software installed, even the slack-build may
fail.
So doing it the way I described above should be the way if you want more control
on the build process.

The packages I produced are created on fresh installed vms. So they should work
out if the box.

Accessing the repo has the advantage that you will stay up to date to any
upcoming changes. That would not possible with a source package as it only
contains "released" source code.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > "simbad" <Han### [at] gmxde> wrote:
> > > Hi ho,
> > > there are two packages available.
> > > ...
>
> git clone https://github.com/tribad/povmodeler.git
> cd povmodeler
> git checkout slackware14.x
> cmake .
> make
> make install

> ...
> Accessing the repo has the advantage that you will stay up to date to any
> upcoming changes. That would not possible with a source package as it only
> contains "released" source code.

sure.  I simply assumed that "available packages" means released, and are based
on "released" code bases  (must be my age ;-)).  thanks though.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > "jr" <cre### [at] gmailcom> wrote:
> > > "simbad" <Han### [at] gmxde> wrote:
> > > > Hi ho,
> > > > there are two packages available.
> > > > ...
> >
> > git clone https://github.com/tribad/povmodeler.git
> > cd povmodeler
> > git checkout slackware14.x
> > cmake .
> > make
> > make install
>
> > ...
> > Accessing the repo has the advantage that you will stay up to date to any
> > upcoming changes. That would not possible with a source package as it only
> > contains "released" source code.
>
> sure.  I simply assumed that "available packages" means released, and are based
> on "released" code bases  (must be my age ;-)).  thanks though.
>
>
> regards, jr.

I dont think I will really "release" any version with the old code as it is hard
to maintain and is in many ways complicated.
But on the other hand I want to keep on to support the old users as good as
possible. I already started a rewrite of the GUI but this will take some time.
So I split my time between support for the old code and to rewrite the GUI.

But the build environment and packaging will be needed in both development
pathes.

For handling of bugs I think it would be best to use the github issue tracker.
This would help to establish something near to release managment.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> > ...
> I dont think I will really "release" any version with the old code as it is hard
> to maintain and is in many ways complicated.
> But on the other hand I want to keep on to support the old users as good as
> possible. I already started a rewrite of the GUI but this will take some time.

something to look forward to.  :-)

> So I split my time between support for the old code and to rewrite the GUI.
>
> But the build environment and packaging will be needed in both development
> pathes.
>
> For handling of bugs I think it would be best to use the github issue tracker.

ok.

> This would help to establish something near to release managment.

yes, be(com)ing the package maintainer/developer for a software with an existing
user base is a pretty big hat to wear, I think.  wishing you good fortune.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > > ...
> > I dont think I will really "release" any version with the old code as it is hard
> > to maintain and is in many ways complicated.
> > But on the other hand I want to keep on to support the old users as good as
> > possible. I already started a rewrite of the GUI but this will take some time.
>
> something to look forward to.  :-)
>
> > So I split my time between support for the old code and to rewrite the GUI.
> >
> > But the build environment and packaging will be needed in both development
> > pathes.
> >
> > For handling of bugs I think it would be best to use the github issue tracker.
>
> ok.
>
> > This would help to establish something near to release managment.
>
> yes, be(com)ing the package maintainer/developer for a software with an existing
> user base is a pretty big hat to wear, I think.  wishing you good fortune.
>
>
> regards, jr.

So ....

found the segfault bug. Fixed some other things from making it run on slackware
and created all packages anew. Because of the work done it gives a new
version-number (only the patch-level).

https://www.simulated-universe.de/povmodeler-1.1.5-debian-10.deb
https://www.simulated-universe.de/povmodeler-1.1.5-linuxmint-18.3.deb
https://www.simulated-universe.de/povmodeler-1.1.5-linuxmint-19.1.deb
https://www.simulated-universe.de/povmodeler-1.1.5-linuxmint-19.2.deb
https://www.simulated-universe.de/povmodeler-1.1.5-opensuse-leap-15.1.rpm
https://www.simulated-universe.de/povmodeler-1.1.5-x86_64-14.1.tgz
https://www.simulated-universe.de/povmodeler-1.1.5-x86_64-14.2.tgz

The slackware packages are the two last with no distro name in them.
Just try it and please report bugs on github. Help can be obtained here.
Questions answered as well.

But I hope I can spend more time on the rewrite.

Post a reply to this message