* Stefano Lattarini wrote on Thu, Dec 16, 2010 at 10:51:15PM CET:
> Currently, the MANS primary accept *all* the standard automake
> builtin prefix dirs (from lib and bin to pkglibexec and sysconf).
>
> IMHO it should accept only man and man{1..9} (maybe doc? but I'd
> rather say no).
This one is
* Stefano Lattarini wrote on Thu, Dec 16, 2010 at 10:52:10PM CET:
> Currently, the TEXINFOS primary accept *all* the standard automake
> builtin prefix dirs (from `lib' and `bin' to `pkglibexec' and
> `sysconf').
>
> IMHO it should accept only the `info' prefix (maybe also `doc'? but
> I'd rather
On 12/16/10 18:19, Stefano Lattarini wrote:
> Hello Ralf and Behdad.
>
> On Wednesday 17 November 2010, Behdad Esfahbod wrote:
>>
>> On 11/13/10 03:00, Ralf Wildenhues wrote:
>>>
>>> You are the first person to report this in the 12 months since we
>>> released fixed versions of Automake. I don't
Hello Ralf and Behdad.
On Wednesday 17 November 2010, Behdad Esfahbod wrote:
>
> On 11/13/10 03:00, Ralf Wildenhues wrote:
>>
>> You are the first person to report this in the 12 months since we
>> released fixed versions of Automake. I don't have other data to go on
>> but it thus doesn't seem t
On Fri, Dec 17, 2010 at 7:02 AM, Ralf Wildenhues wrote:
> [ no need to keep bug-automake@ in Cc:; debbugs takes care of that ]
Noted.
> * Jack Kelly wrote on Thu, Dec 16, 2010 at 08:42:52PM CET:
>> > Disagree. foo.info should always be built, because it goes into `make
>> > dist'.
>
> Ah, a piec
Currently, the TEXINFOS primary accept *all* the standard automake
builtin prefix dirs (from `lib' and `bin' to `pkglibexec' and
`sysconf').
IMHO it should accept only the `info' prefix (maybe also `doc'? but
I'd rather say no).
Thanks,
Stefano
Currently, the MANS primary accept *all* the standard automake
builtin prefix dirs (from lib and bin to pkglibexec and sysconf).
IMHO it should accept only man and man{1..9} (maybe doc? but I'd
rather say no).
Thanks,
Stefano
[ no need to keep bug-automake@ in Cc:; debbugs takes care of that ]
Hello Jack,
* Jack Kelly wrote on Thu, Dec 16, 2010 at 08:42:52PM CET:
> On Fri, Dec 17, 2010 at 6:41 AM, Jack Kelly wrote:
> > On Fri, Dec 17, 2010 at 6:09 AM, Ralf Wildenhues wrote:
> >> if COND
> >> info_TEXINFOS = foo.texi
>
On Fri, Dec 17, 2010 at 6:09 AM, Ralf Wildenhues wrote:
> if COND
> info_TEXINFOS = foo.texi
> foo_TEXINFOS = bar.texi
> nodist_info_TEXINFOS = generated.texi
> endif
>
> should work to generate and install foo.{info,pdf,...} only if COND,
> but distribute foo.texi and bar.texi always. Similar wi
On Fri, Dec 17, 2010 at 6:41 AM, Jack Kelly wrote:
> On Fri, Dec 17, 2010 at 6:09 AM, Ralf Wildenhues
> wrote:
>> if COND
>> info_TEXINFOS = foo.texi
>> foo_TEXINFOS = bar.texi
>> nodist_info_TEXINFOS = generated.texi
>> endif
>>
>> should work to generate and install foo.{info,pdf,...} only if
* Stefano Lattarini wrote on Thu, Dec 16, 2010 at 06:40:37PM CET:
> In section "3.3 The Uniform Naming Scheme" I read:
>
> ``The current primary names are ‘PROGRAMS’, ‘LIBRARIES’, ‘LISP’,
>‘PYTHON’, ‘JAVA’, ‘SCRIPTS’, ‘DATA’, ‘HEADERS’, ‘MANS’, and
>‘TEXINFOS’. Some primaries also allow a
The subjects says it all, basically.
In section "3.3 The Uniform Naming Scheme" I read:
``The current primary names are ‘PROGRAMS’, ‘LIBRARIES’, ‘LISP’,
‘PYTHON’, ‘JAVA’, ‘SCRIPTS’, ‘DATA’, ‘HEADERS’, ‘MANS’, and
‘TEXINFOS’. Some primaries also allow additional prefixes that
control oth
12 matches
Mail list logo
