[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: VCS=(yes|always)
From: |
Kaloian Doganov |
Subject: |
Re: VCS=(yes|always) |
Date: |
Sun, 27 Jan 2008 15:44:49 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gNewSense gnu/linux) |
Yavor Doganov <address@hidden> writes:
> I understand your reasons, but this solution defeats a basic
> convention.
I don't see how, when the build behaves exactly as expected.
Please note that I do not question the results, but the implementation
(and even just one aspect of it). The basic convention I'm refering to
is stated in the GNU Coding Standards:
Each program-name variable should come with an options variable that
is used to supply options to the program.
By having CVS and CVSOPTS variables we're misleading the reader of the
GNUmakefile to make assumtions about how these variables relate to each
other. I think we should avoid this if it is not very hard.
That's what's bugs me, but it is not the most important thing in the
world.
- trans-coord/gnun/prep/gnun ChangeLog GNUmakefil..., Yavor Doganov, 2008/01/26
- VCS=(yes|always), Kaloian Doganov, 2008/01/26
- Re: VCS=(yes|always), Yavor Doganov, 2008/01/26
- Re: VCS=(yes|always), Kaloian Doganov, 2008/01/26
- Re: VCS=(yes|always), Yavor Doganov, 2008/01/26
- Re: VCS=(yes|always), Yavor Doganov, 2008/01/26
- Re: VCS=(yes|always), Kaloian Doganov, 2008/01/27
- Re: VCS=(yes|always), Yavor Doganov, 2008/01/27
- Re: VCS=(yes|always), Yavor Doganov, 2008/01/27
- Re: VCS=(yes|always),
Kaloian Doganov <=
- Re: VCS=(yes|always), Yavor Doganov, 2008/01/27