Frank Küster wrote:
> Steve Langasek wrote:
>
>> On Thu, Dec 03, 2009 at 11:40:06AM +0100, Frank Küster wrote:
>>> However, and here's the policy-related problem: Of course the admin
>>> might have changed the default paper for one particular binary
>>> manually. What should I do in this case?
>
Steve Langasek wrote:
> On Thu, Dec 03, 2009 at 11:40:06AM +0100, Frank Küster wrote:
>> However, and here's the policy-related problem: Of course the admin
>> might have changed the default paper for one particular binary
>> manually. What should I do in this case?
>
> [...]
>
>> - let libpaper'
On Thu, Dec 03, 2009 at 11:40:06AM +0100, Frank Küster wrote:
> However, and here's the policy-related problem: Of course the admin
> might have changed the default paper for one particular binary
> manually. What should I do in this case?
[...]
> - let libpaper's setting overwrite everything: Pr
On Do, 03 Dez 2009, Roger Leigh wrote:
> Can the TeX configuration files source other configuration files?
Some can some cannot.
> If this is the case, can't each of the separate configuration files
> source a single file which defines only the papersize? This way
No, that is definitely impossi
On Thu, Dec 03, 2009 at 11:40:06AM +0100, Frank Küster wrote:
> Are there any other options? Currently, the configuration files in
> question are all conffiles; we'd have to change that, too, I guess. I
> have not followed this field in the last years; I guess ucf is still the
> method of choice i
Hi,
I had thought that I had understood it. But somehow I'm again running
into problems when it comes to manipulating configuration files with
maintainer scripts.
TeXLive contains many binaries that change output depending on the
papersize used. Each of them has a configuration file which - amon
6 matches
Mail list logo
