reassing 354113 tex-common
thanks
I think this problem is of general interest, or at least I don't feel we
(the TeX Task Force) cannot decide this on our own.
In short: May a package assume that package builds are performed with
root-like rights, and thus use non-world-writable directories for
Le Jeudi 23 Février 2006 16:37, Frank Küster a écrit :
So the current state is: If pbuilder runs all commands inside the
chroot, everything is fine, and AFAIK the same is true for the buildds.
But if you su to some user in the chroot, near to every package that
Build-depends on tetex-bin will
Hi,
Frank Küster wrote:
In short: May a package assume that package builds are performed with
root-like rights, and thus use non-world-writable directories for
caching purposes?
Absolutely not. The only assumption you may make is that the binary*
targets are called in a way that allows
Daniel Schepler [EMAIL PROTECTED] wrote:
Le Jeudi 23 Février 2006 16:37, Frank Küster a écrit :
So the current state is: If pbuilder runs all commands inside the
chroot, everything is fine, and AFAIK the same is true for the buildds.
But if you su to some user in the chroot, near to every
Simon Richter [EMAIL PROTECTED] wrote:
Hi,
Frank Küster wrote:
In short: May a package assume that package builds are performed with
root-like rights, and thus use non-world-writable directories for
caching purposes?
Absolutely not.
...because?
Because:
, Policy 4.8
| The build
Le Jeudi 23 Février 2006 17:20, Frank Küster a écrit :
For example, I just tried running pbuilder on
make_3.80+3.81.b4-1.dsc again, which does create some fonts during the
build, and the build completes fine, except that I get error messages
like kpathsea: Running mktexpk --mfmode ljfour
Daniel Schepler wrote:
Here's a thought: how hard would it be to make TeX fall back to caching in a
directory under the user's home directory (maybe $HOME/.fonts/texmf or so) if
it can't write to /var/cache/fonts? pbuilder does have $HOME set up to work
all right with BUILDUSER{ID,NAME}.
Daniel Schepler [EMAIL PROTECTED] wrote:
Here's a thought: how hard would it be to make TeX fall back to caching in a
directory under the user's home directory (maybe $HOME/.fonts/texmf or so) if
it can't write to /var/cache/fonts?
It would be extremely hard (at least 5 different shell
Thomas Viehmann [EMAIL PROTECTED] wrote:
Daniel Schepler wrote:
Here's a thought: how hard would it be to make TeX fall back to caching in a
directory under the user's home directory (maybe $HOME/.fonts/texmf or so)
if
it can't write to /var/cache/fonts? pbuilder does have $HOME set up
[Frank Küster]
Because:
, Policy 4.8
| The build target must not do anything that might require root privilege.
`
Right, but the 'binary' target is run as root.
, Policy 4.8
| The `fakeroot' package often allows one to build a package correctly
| even without being root.
10 matches
Mail list logo
