Re: Bootfile locations for rbootd?

1998-06-19 Thread Peter Maydell
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
[rbootd directory choice]
the usual problem : you have an application and need an application home.
with ftp it's /home/ftp, for web server /var/www, and for many other stuff
it's currently /var/lib/package or /var/spool/package.

but with slink you should use fhs, so it's ???
/var/state/package /var/cache/package and /var/spool/package
are possible : 
 - cache for data, that can get lost and regenerated
 - state for more permanent data
 - spool ... something in the middle. it exists for compatibility reasons :-)

Hmm. Is the local sysadmin allowed to put random files in /var/ ?
I thought you couldn't guarantee that the distribution wouldn't stomp on
them... [if the local admin can't add files then the package is useless
because it provides no boot images itself :-]

do not use :
 /usr/local/*  distributions should not touch that tree

But in this case we aren't really using it; we're just saying 'if you put
files in this directory then rbootd will serve them'. The policy manual
explicitly says that we can create directories under /usr/local; is this
advice now out of date?

IMHO the right thing would be for rbootd to be able to accept more than
one directory, specified in the configuration file rather than at
compile time. Then we could have /var/whatever and the local sysadmin
could use /usr/local/whatever. But that's not totally trivial as it 
requires some restructuring of the way the daemon works...

Peter Maydell
[I suppose I'm the upstream maintainer, BTW :- (and the NetBSD guys
are upstream of me, until I get round to submitting my patches...)]


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Bug#23522: man-db installs foreign language manpages

1998-06-15 Thread Peter Maydell
Fabrizio Polacco wrote:
On Sun, Jun 14, 1998 at 11:10:13PM +0200, Peter Maydell wrote:
 man-db installs Spanish, Italian and German versions of its manpages,
 as well as English ones.

This is one of the goals of Debian.
It is surely the main reason for *my* partacipation to the project.
When I find a package wich doesn't install all the translations
available in its sources, I raise a bug asking to do so.

My point wasn't that installing man pages for multiple languages was
wrong, just that installing them without asking was wrong.

 This might not seem like a significant disk usage for this package
 (it's about 25K extra for each language), but consider if every
 program installed four versions.

Then the necessity to have such decision tool will become urgent, and
the tool will be done. If I drop translations, this will never be done.

You're probably right here. My intention in filing this bug report
was more to bring up this point as a general problem. It's not a bug
against man-db in the sense of 'this must be fixed immediately'.
[but on the other hand I'm not sure severity: wishlist is right either]

 My /usr/man/man?/ tree is about 5MB,
 and I would certainly object if Debian installed an unnecessary extra
 15MB of man pages I would never read.

Your opinion that translations are unnecessary extras is only your
opinion. My aim is to create a multilingual distribution. 

They're unnecessary extras *on my machine*. If I don't want a web
server on my machine, I don't install that package. If I don't want
the Linux HOWTOs, I don't install doc-linux-text. If I don't want
Spanish documentation, I should be able to not install it.

Presumably this is (will be) a problem for (eg) German users too -- why
should they have Spanish man pages *unless they ask for them*?

My preferred
example for this is a shell machine in a ISP in Europe

Obviously some admins will want all language versions. But they are
in the minority and Debian ought to cater for the rest of us too.

If you don't reassign this bug to dpkg or apt, I will close it in two
days (as later I will be busy).

rant
Oi! I'm an end user (OK, so I browse debian-devel :-). I'm not supposed
to have to know how to manipulate the bug tracking system. I agree that
man-db might not be the right place for this bug report, but I wasn't
sure where to file bugs against programs that don't exist (our hypothetical
language management tool) so I picked the only package on my system with
multiple-language manpages. If you don't think it's filed against the
right package, it's *your* responsibility as a developer to reassign
it to the right place.
/rant
[In fact, I probably could reassign it, if I read the BTS documentation; 
but as a point of principle you shouldn't ask me to :-]

Peter Maydell


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]