Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

Hi, Is it OK to request these sorts of conversations take place someplace else? I did not know before that there's a lot of heated conversations. I don't want to have to read these. Please be considerate. Or agree on something and move on, may be? Ethan On Sun, Nov 13, 2016 at 1:43 AM,

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

On Sun, Nov 13, 2016 at 05:13:22PM +, Thomas Adam wrote: > On Sun, Nov 13, 2016 at 04:09:14PM +0100, Dominik Vogt wrote: > > Bofore you start working on that, please take a look at the > > dv/fix-transform-name branch. > > OK, this looks good. I'm surprised that FvwmCommand.sh is installed

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

On Mon, Nov 14, 2016 at 01:52:51AM +0100, Dominik Vogt wrote: > It's still not good. Isn't there a standard Automake way to > install shell scripts? IIRC, there's bin_SCRIPTS -- ah, poking around reveals this: https://www.gnu.org/software/automake/manual/html_node/Scripts.html Although we're

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

Please don't top post on the fvwm lists. On Mon, Nov 14, 2016 at 12:44:47AM +, Ethan Raynor wrote: > it's those points i would like to see put elsewhere I've completely understood that it bothers you. If you don't want to read it, don't. This is an unavoidable part of public software

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

Hi, I can understand personal opinions - they're important and they happen all the time with projects, I understand that. But I don't think it is very fair to say I should not read it - when I won't know weather it's there or not to start with. So I think just not having those conversations is

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

On Mon, Nov 14, 2016 at 12:58:42AM +, Thomas Adam wrote: > On Mon, Nov 14, 2016 at 01:52:51AM +0100, Dominik Vogt wrote: > > By the way, any idea why "make distcheck" has never caught the > > faulty uninstallation of the symlinks? > > Nope, no idea. > > I find dist/distcheck to be some

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

On Mon, Nov 14, 2016 at 12:07:42AM +, Ethan Raynor wrote: > Is it OK to request these sorts of conversations take place someplace > else? No. If there's one place for discussing fvwm development, it's this mailing list. Ciao Dominik ^_^ ^_^ -- Dominik Vogt

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

On Mon, Nov 14, 2016 at 01:11:57AM +, Ethan Raynor wrote: > I can understand personal opinions - they're important and they happen > all the time with projects, I understand that. But I don't think it is > very fair to say I should not read it - when I won't know weather it's > there or not to

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

On Sun, Nov 13, 2016 at 02:06:19AM +, Thomas Adam wrote: > On Sun, Nov 13, 2016 at 02:43:13AM +0100, Dominik Vogt wrote: > > Why on earth do we have to repeat the mistake of the past by > > putting the version number in the project name *again*? Every > > other project manages backwards

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

On Sun, Nov 13, 2016 at 02:03:52PM +, Thomas Adam wrote: > On Sun, Nov 13, 2016 at 04:30:23AM +0100, Dominik Vogt wrote: > > On Sun, Nov 13, 2016 at 02:06:19AM +, Thomas Adam wrote: > > > On Sun, Nov 13, 2016 at 02:43:13AM +0100, Dominik Vogt wrote: > > > > Why on earth do we have to

Request for testing help

Hi folks, I'm still struggling with reproducing a creash in the a crash in the branch dv/new-parser-2. It has something to do with passing around arguments from one complex function to another (possibly nested deeper). In some situations, the memory for an argument is freed while still being in

Re: [fvwmorg/fvwm] f508f5: Fix installation and uninstallation with --program...

On Sun, Nov 13, 2016 at 07:00:29AM -0800, Dominik Vogt wrote: > Branch: refs/heads/dv/fix-program-transform > Home: https://github.com/fvwmorg/fvwm > Commit: f508f5f574de461e21fa5ad2d4d2d50eb75378df > > https://github.com/fvwmorg/fvwm/commit/f508f5f574de461e21fa5ad2d4d2d50eb75378df

default-config installation

This is not how to install files with automake: default-config/Makefile.am: > ## Process this file with automake to create Makefile.in > > configdir = @FVWM_DATADIR@/default-config > inst_location = $(DESTDIR)@FVWM_DATADIR@/default-config > config_DATA = config \ > .stalonetrayrc \

[fvwmorg/fvwm] f508f5: Fix installation and uninstallation with --program...

Branch: refs/heads/dv/fix-program-transform Home: https://github.com/fvwmorg/fvwm Commit: f508f5f574de461e21fa5ad2d4d2d50eb75378df https://github.com/fvwmorg/fvwm/commit/f508f5f574de461e21fa5ad2d4d2d50eb75378df Author: Dominik Vogt Date: 2016-11-13 (Sun,

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

On Sun, Nov 13, 2016 at 02:03:52PM +, Thomas Adam wrote: > On Sun, Nov 13, 2016 at 04:30:23AM +0100, Dominik Vogt wrote: > > On Sun, Nov 13, 2016 at 02:06:19AM +, Thomas Adam wrote: > > > On Sun, Nov 13, 2016 at 02:43:13AM +0100, Dominik Vogt wrote: > > > > Why on earth do we have to