From: Stuart Lamble [EMAIL PROTECTED]
Just a suggestion (and probably not a very good one): where a package needs
to ask a question, perhaps it'd be appropriate to have a script
postinst.questions (or some such) which can be run after all the other
packages have been installed and configured?
Bruce Perens:
Another possibility would be to have a script that runs immediately when
you select the package using dselect, before the package is unpacked, and
squirrels away your input for later. Of course, we'd have to run it from
dpkg if dselect was not used.
Discussion, please?
I'd
I'd like some (easy) way of storing answers to questions. The
questions and answers could be shared between packages, when
suitable. One such question would be whether the local admin
wants to allow creation of the empty directories in /usr/local.
If we want to be ambitious, we'll create a
Dear Bruce,
you wrote:
Let's please not add unnecessary questions in the postinst.
I think /usr/local should be a symbolic link to /local, but it should
always exist.
We will not gain anything with this! I am sure if you think about it
you will recognize that this will just shift the
Bruce:
Let's please not add unnecessary questions in the postinst.
I think /usr/local should be a symbolic link to /local, but it should
always exist.
From: Dominik Kubla [EMAIL PROTECTED]
We will not gain anything with this! I am sure if you think about it
you will recognize that this will
Hello Ian,
you wrote:
In order that the system administrator may know where to place
additional files a package should create an empty directory in the
appropriate place in /usr/local by supplying it in the filesystem
archive for unpacking by dpkg. The /usr/local directory
Richard Kaszeta writes (/usr/local (again)):
...
Since packages generally don't install anything other than empty dirs
in /usr/local, can't this be handled in a way that makes it easier for
those of us trying to maintain many debian machines?
Section 3.2.9 of the policy manual may
Just an idea, no flames, etc intended:
Could maintainers who have packages that create directories/etc in
/usr/local make sure they do it in a way that is friendly to
nfs-mounted /usr/local?
Example:
On all of our debian 1.1 machines, /usr/local is an nfs mounted
directory, and on all but one
Richard Kaszeta writes:
Just an idea, no flames, etc intended: Could maintainers who have
packages that create directories/etc in /usr/local make sure they do
it in a way that is friendly to nfs-mounted /usr/local?
I second that! AMOF i did bring that up some time ago, but somehow we
I sort of thought we had settled on (a). Although I would normally
expect /usr/*local* to be local, I don't see any reason not to be
friendly to unusual setups especially in the case of (c) where it
doesn't cost anything, assuming the base package puts in a reasonable
default.
Well, in my case
10 matches
Mail list logo
