Re: Maintaining a non-US package?
In article <19981105021750.A8985@ormond.unimelb.edu.au>, Chris Leishman <email@example.com> writes:
> On Wed, Nov 04, 1998 at 11:14:48PM +1100, Hamish Moffatt wrote:
>> On Sat, Oct 31, 1998 at 06:48:51PM +1100, Chris Leishman wrote: >
>> The postinst modifies the /etc/exports file to add a 2 lines as
>> I don't know about /crypt etc; obviously the FSSTND/FHS doesn't
>> exactly say anything about it. But modifying another package's
>> configuration files (ie /etc/exports) is not allowed.
>> Unless the nfs-server package provides a mechanism for you to add
>> stuff to /etc/exports, you have to let the user do it.
> Hmm...thats annoying (but probably reasonable). I would, however,
> like to make the installation as transparent as possible, without
> complicating the matter with making the user add stuff by hand (and
> having to explain why). The major problem in this case is that the
> package relies very, very heavily on the nfs system, and won't work
> without a dummy entry in there....
> Is it reasonable to prompt the user and ask if they would like it
> added (and removed at postinst)? Or is that still bad?
Yes, unfortunately. You could make an /etc/exports.cfs file, and tell
the user to move that into place. Or work with the nfs server
maintainers to work out a way to add/remove export programmatically.
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>