Re: Other FHS issues (was Re: /usr/share/doc: some new proposals)

1999-08-06 Thread Santiago Vila
On 5 Aug 1999, Chris Waters wrote: > Julian Gilbey <[EMAIL PROTECTED]> writes: > > > (I think the issue was with the /usr/doc->/usr/share/doc move, not > > with FHS compliance. > > Yes, I'm trying to see the big picture, though. Why are we moving to > /usr/share/doc? FHS. Well, then, what ab

Re: Other FHS issues (was Re: /usr/share/doc: some new proposals)

1999-08-05 Thread Chris Waters
Julian Gilbey <[EMAIL PROTECTED]> writes: > (I think the issue was with the /usr/doc->/usr/share/doc move, not > with FHS compliance. Yes, I'm trying to see the big picture, though. Why are we moving to /usr/share/doc? FHS. Well, then, what about the FHS, are we close? No. So the only thing

Re: Other FHS issues (was Re: /usr/share/doc: some new proposals)

1999-08-05 Thread Julian Gilbey
> I could swear that a couple of people *DID* say exactly that -- that > if we fix debhelper and whatever the other tool is, we'll only have a > handful of packages left to fix. Obviously, you and *I* know this is > pretty darned unlikely to happen by Potato's release! :-) (I think the issue was

Other FHS issues (was Re: /usr/share/doc: some new proposals)

1999-08-04 Thread Chris Waters
Manoj Srivastava <[EMAIL PROTECTED]> writes: > Hi, > >>"Chris" == Chris Waters <[EMAIL PROTECTED]> writes: > Chris> There is more involved with FHS than I think many people > Chris> realize. We have a fair amount of work to do just with the > Chris> stuff that is obvious *and* non-contentious

The "four objections" thing (was Re: /usr/share/doc: some new proposals)

1999-08-04 Thread Chris Waters
Manoj Srivastava <[EMAIL PROTECTED]> writes: > A nit pick: the policy update proposal does not have the > weight of policy. It is merely a convention, or guidelines. Yes, very good thing to keep in mind. > If the issue raised is especially contentious, or is deemed to be > sui

Re: /usr/share/doc: some new proposals

1999-08-04 Thread Joey Hess
Giuliano Procida wrote: > Peoples' score files (analogous to "documentation") are no longer > where they expect them. This is not so serious. I think this is a non-issue. Who reads score files by hand? Most are binary files anyway. The games will know where to look. > However, the save > files ne

Re: /usr/share/doc: some new proposals

1999-08-04 Thread Giuliano Procida
Hi. Sorry to stick my oar in again. On Wed, Aug 04, 1999 at 01:11:06AM -0500, Manoj Srivastava wrote: > Hi, > >>"Chris" == Chris Waters <[EMAIL PROTECTED]> writes: > > Chris> There is more involved with FHS than I think many people > Chris> realize. We have a fair amount of work to do just wit

Re: /usr/share/doc: some new proposals

1999-08-04 Thread Manoj Srivastava
Hi, >>"Chris" == Chris Waters <[EMAIL PROTECTED]> writes: Chris> No, I didn't object to the idea, I objected to the proposal. And by Chris> the way, I don't see *anything* about "five formal objections" in the Chris> policy proposal policy. A nit pick: the policy update proposal does

Re: /usr/share/doc: some new proposals

1999-08-04 Thread Manoj Srivastava
Hi, >>"Chris" == Chris Waters <[EMAIL PROTECTED]> writes: Chris> There is more involved with FHS than I think many people Chris> realize. We have a fair amount of work to do just with the Chris> stuff that is obvious *and* non-contentious, like Chris> /usr/share/man and /usr/share/info. I

Re: /usr/share/doc: some new proposals

1999-08-02 Thread Chris Waters
Marcus Brinkmann <[EMAIL PROTECTED]> writes: > On Sun, Aug 01, 1999 at 02:05:17PM +1000, Anthony Towns wrote: > > > DELAYED DO-NOTHING (the Bad One) > > Honestly, I don't even think this is that bad. > > > > Anyway, I think the more important part of this discussion, or at > > least the more co

Re: /usr/share/doc: some new proposals

1999-08-02 Thread Chris Waters
Anthony Towns writes: > > DELAYED DO-NOTHING (the Bad One) > Honestly, I don't even think this is that bad. Ok, a couple of other people have said the same thing, and so maybe it's not so bad. Maybe the best way to deal with the symlink idea is to make it optional (after potato), and entirely

Re: /usr/share/doc: some new proposals

1999-08-01 Thread Chris Waters
Marcus Brinkmann <[EMAIL PROTECTED]> writes: > Move to usr/share/doc in individual packages. Do nothing else. No symlinks, > no messing with dpkg, no scripts. A number of people have objected to that proposal already! Several users have stated that they *hate* the idea. If we care about our use

Re: /usr/share/doc: some new proposals

1999-08-01 Thread Marcus Brinkmann
On Sun, Aug 01, 1999 at 02:05:17PM +1000, Anthony Towns wrote: > > > DELAYED DO-NOTHING (the Bad One) > > Honestly, I don't even think this is that bad. > > Anyway, I think the more important part of this discussion, or at > least the more controversial part, is whether symlinks/cronjobs/hacking

Re: /usr/share/doc: some new proposals

1999-08-01 Thread Anthony Towns
On Sat, Jul 31, 1999 at 06:59:11PM -0700, Chris Waters wrote: > At worst, we'll be in this same position at the *beginning* of a > release cycle, and that alone has one advantage: it increases the > *chance* that we can get a sweeping change done before the next > release. *shrug*. It's still only

/usr/share/doc: some new proposals

1999-08-01 Thread Chris Waters
Anthony Towns writes: > [1 ] > On Sat, Jul 31, 1999 at 12:40:39AM -0700, Chris Waters wrote: > > * Stick with /usr/doc until potato is released, then begin a massive > > migration, which may or may not involve symlinks. > > - we can't pretend FHS compliance (but we couldn't anyway). > >