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

[Thomas Adam]

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 incompatible releases just fine,
> only fvwm changes its name with each major release.  This just
> complicates things, and helps nobody.  That's what configure's
> binary suffix is for.

So what would you rather, and to what extent should this happen?  If you don't
have the time to do the work, at least have the courtesy to say so and provide
a list of things you want, and it'll get done.  But to keep going silent for a
while, coming back, and then bemoaning the state of things because you weren't
around, and/or didn't get asked, and/or things werent done how you would have
wanted, isn't how projects are run, or indeed, *will not* be run for as long
as I am involved with them.

> fvwm yet again.  And I've got to rewrite it *again*, manage two
> different configs and fiddle with two repos in parallel, just to
> be able to install two versions in parallel, which is already
> possible (and if not, this needs to be fixed anyway).

It's all a little bit "moan, moan, moan" coming from you, with there being
little evidence of anything actually wrong, other than you don't like
something.  So far, I've been kind.  So far, I've been courteous and polite in
helping you and explaining all that I can.  But I cannot work with just that
alone, Dominik.  I can't help *you* or give assistance when the rhetoric
you're throwing out is intangible.  I've just _told_ you how you can
accomplish certain tasks.  If you actually have something sensible which you
need help with, then by all means ask me for help if you need it.  But please
stop whinging.

> By the way, everybody else would call their versions fvwm-2 and
> fvwm-3, and that's what I'll do, starting now.

So what I want from you is a list of things which aren't correct.  You say you
want "fvwm-2" and "fvwm-3".  Fine, I don't mind what it's called, provided
some choice is made.

-- Thomas Adam

[fvwmorg/fvwm3] d58219: Change version to 3.0.0

[Thomas Adam]

  Branch: refs/heads/master
  Home:   https://github.com/fvwmorg/fvwm3
  Commit: d58219c5c32f1e430db15d4bc0008a36239c3030
  
https://github.com/fvwmorg/fvwm3/commit/d58219c5c32f1e430db15d4bc0008a36239c3030
  Author: Thomas Adam 
  Date:   2016-11-12 (Sat, 12 Nov 2016)

  Changed paths:
M .gitignore
M TODO.md
M bin/Makefile.am
M configure.ac
M doc/fvwm/Makefile.am
M fvwm/Makefile.am
R fvwm/fvwm.c
A fvwm/fvwm3.c
M libs/Makefile.am
R libs/fvwmlib.c
A libs/fvwmlib3.c
M modules/FvwmAnimate/Makefile.am
M modules/FvwmAuto/Makefile.am
M modules/FvwmBacker/Makefile.am
M modules/FvwmBanner/Makefile.am
M modules/FvwmButtons/Makefile.am
M modules/FvwmCommand/Makefile.am
M modules/FvwmConsole/Makefile.am
M modules/FvwmCpp/Makefile.am
M modules/FvwmEvent/Makefile.am
M modules/FvwmForm/Makefile.am
M modules/FvwmIconMan/Makefile.am
M modules/FvwmIdent/Makefile.am
M modules/FvwmM4/Makefile.am
M modules/FvwmPager/Makefile.am
M modules/FvwmProxy/Makefile.am
M modules/FvwmRearrange/Makefile.am
M modules/FvwmScript/Makefile.am
M tests/hints/Makefile.am
M utils/Makefile.am
M utils/fvwm-version-str.sh

  Log Message:
  ---
  Change version to 3.0.0

Indicate this is fvwm-3.0.0


  Commit: 65ba209215f9b8b27bee38c7382f1999126cc6f1
  
https://github.com/fvwmorg/fvwm3/commit/65ba209215f9b8b27bee38c7382f1999126cc6f1
  Author: Thomas Adam 
  Date:   2016-11-13 (Sun, 13 Nov 2016)

  Changed paths:
M README.md

  Log Message:
  ---
  Update README


Compare: https://github.com/fvwmorg/fvwm3/compare/e8ab7a826310...65ba209215f9

Re: symbolic links in default-config/Makefile.am

[Thomas Adam]

On Sat, Nov 12, 2016 at 04:26:55PM +0100, Harald Dunkel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Hi folks,
> 
> default-config/Makefile.am says
> 
> install-data-hook:
>   cp -r $(srcdir)/images $(inst_location)
>   ln -sf $(inst_location)/FvwmScript-DateTime $(inst_location)/..
>   ln -sf $(inst_location)/FvwmScript-ConfirmQuit $(inst_location)/..
>   ln -sf $(inst_location)/FvwmScript-ConfirmCopyConfig $(inst_location)/..
> 
> Since inst_location is an absolute path this makes the fvwm installdir
> non-relocatable. Do you think this could be fixed, e.g. by using hard
> links instead?

Not for 2.6.7, no.  I might do this for an eventual 2.6.8, but I won't be
making that version just for this; there'd have to be other changes first.

-- Thomas Adam

symbolic links in default-config/Makefile.am

[Harald Dunkel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi folks,

default-config/Makefile.am says

install-data-hook:
cp -r $(srcdir)/images $(inst_location)
ln -sf $(inst_location)/FvwmScript-DateTime $(inst_location)/..
ln -sf $(inst_location)/FvwmScript-ConfirmQuit $(inst_location)/..
ln -sf $(inst_location)/FvwmScript-ConfirmCopyConfig $(inst_location)/..

Since inst_location is an absolute path this makes the fvwm installdir
non-relocatable. Do you think this could be fixed, e.g. by using hard
links instead?


Thanx in advance
Harri
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAlgnNL4ACgkQCp4qnmbT
gctMzAgAgBGgUbgh+yi4Z+RXaMA8mZMZ81cK3b7pJpLnaBA/GLPE1ubxk6fjDVhz
s6SMF2Jp7+xQ6ClrzSpDRiGJsH9LqZNYyGR2cviDVH0vhLWQLsBPw30yhhk7AGen
TFgx+Z4fSgrF/jbAAjRQSjn/evuaQyf3FLiPux5jx5VCq6cHrWFA3xAq7x9kZ/q1
K1sS4zjhr7DYUhPi1KTeVPGfKC27E2ENI0mpwOrRRVatXTB452dHYQ3em/D5JlKY
i+9RIfVsu9v2F2DrKDzibIeudRpBzXPcJfJJv90kaQQjeAMRq7kTAO7+HuK+J+JO
s8GhirqIH6JbNueBzYPajEvgk2Xapg==
=3KPa
-END PGP SIGNATURE-