Norbert Preining [EMAIL PROTECTED] wrote:
config.in implementation proposal, please comment:
This looks good to me. Some comments:
#
# first we collect those ls-R files which are group writeable in truegwrite
# and those which are not group writeable in falsegwrite
# furthermore we save
Hi Frank!
On Fre, 07 Okt 2005, Frank Küster wrote:
truegwrite=
falsegwrite=
I don't like these names - truegwrite evokes Trug in my head. Why not
gwritetrue and gwritefalse (if only it sounds more like
[EMAIL PROTECTED])
Well, easy.
for i in var cache main ; do
${i}group=
Norbert Preining [EMAIL PROTECTED] wrote:
for i in var cache main ; do
${i}group=
Sometimes I'm dreaming about using Perl for maintainer scripts. This is
one occation (my %group \dots). Furthermore:
Why not use it. It is possible!
Yes, but Perl code tends to get unreadable, at
Norbert Preining [EMAIL PROTECTED] wrote:
Hi Frank!
On Fre, 07 Okt 2005, Frank Küster wrote:
[...]
else
echo Fixing permissions of ls-R files ...
chmod -v 644 $LSRS 2/dev/null | fgrep changed || true
fi
why the fgrep?
This I took from the tetex-base postinst
Hi Frank!
Attached are my current postinst.in config.in templates
Please comment on it. I send the whole files since the diff is to
complicated.
I have done:
. changed the templates description
. removed the unnecessary templates (groupperm userperm)
. dh_unregister the unnecessary templates
.
Norbert Preining [EMAIL PROTECTED] wrote:
I have done:
. changed the templates description
. removed the unnecessary templates (groupperm userperm)
. dh_unregister the unnecessary templates
. removed the transfer of tetex settings to tex-common
(why did we do it at all? debconf is not a
Hi Frank!
On Fre, 07 Okt 2005, Frank Küster wrote:
*) echo This should not happen: Don't know how to set this! $1 ;;
I finally did:
*) echo select_lsr: don't know how to set this: $1 2 ;;
the 2 is necessary to prevent interaction with debconf.
The cool version (we could save that
Norbert Preining [EMAIL PROTECTED] wrote:
But stop, well, isn't this the whole point of it???
Asume someone managed xyz-ls-R with debconf.
Then changes permissions/owner.
Then realizes that he has to reconfigure tex-common.
Then he calls dpkg-reconfigure -plow tex-common
What should
Hi Frank!
On Don, 06 Okt 2005, Frank Küster wrote:
To me it seems there are two issues here. The first is that our dialog
gives the impression that we do not simply *add* permissions, but
Ok, this is only about the spelling of the managedlsr template, I guess.
This can be fixed easily.
The
Norbert Preining [EMAIL PROTECTED] wrote:
I read through your proposal and have a hard time to understand it. I
wrote a bit of PseudoCode what should be done. What do you think about
this:
Sorry if I was unclear. Maybe I'm also a bit confused. Some of the
errors I found in your text below
Hi Frank!
On Don, 06 Okt 2005, Frank Küster wrote:
of debconf (debconf is not a registry).
Ok, you are right.
alternative suggestion in pseudocode:
config
==
do ls-R files exist? If yes:
- get permissions and ownership of ls-R files for /var/cache/fonts,
/var/lib/texmf and
Package: tex-common
Version: 0.8
Severity: normal
When invoking dpkg-reconfigure tex-common, it is possible to change
permissions of ls-R files from anything (e.g. 644) to 664 by selecting
the corresponding directory. However, when *deselecting* a directory,
the permissions are not changed to
Hi Frank!
On Mit, 05 Okt 2005, Frank Küster wrote:
When invoking dpkg-reconfigure tex-common, it is possible to change
permissions of ls-R files from anything (e.g. 644) to 664 by selecting
the corresponding directory. However, when *deselecting* a directory,
the permissions are not changed
13 matches
Mail list logo
