Re: [PROPOSAL] Allowing crypto in the main archive

2001-01-30 Thread Manoj Srivastava
>>"Steve" == Steve Greenland <[EMAIL PROTECTED]> writes: Steve> On 29-Jan-01, 20:07 (CST), Anthony Towns wrote: >> On Mon, Jan 29, 2001 at 07:34:57PM -0600, Manoj Srivastava wrote: >> > Heh. Sure. I'll do it once. And your proposal has no way of >> > ensuring the tags are either accurat

Re: [PROPOSAL] Allowing crypto in the main archive

2001-01-30 Thread Steve Greenland
On 29-Jan-01, 20:07 (CST), Anthony Towns wrote: > On Mon, Jan 29, 2001 at 07:34:57PM -0600, Manoj Srivastava wrote: > > >>"Anthony" == Anthony Towns writes: > > Anthony> Are you going to go through the distribution and maintain a > > Anthony> list of which packages all these tags apply to, and

Re: CVS srivasta: Updated the build depends; deconf_specification pulls us into the XML worls

2001-01-30 Thread Joey Hess
debian-policy@lists.debian.org wrote: > Log message: > Updated the build depends; deconf_specification pulls us into the XML worls If this is a bad thing, it would probably build as docbook sgml with few changes.. -- see shy jo

Re: Source package policy problem.

2001-01-30 Thread Raul Miller
On Sun, Jan 28, 2001 at 12:14:58AM -0500, Russell Nelson wrote: > Doesn't work because of debian's Filesystem Hierarchy Standard. On Tue, Jan 30, 2001 at 09:02:21AM +0100, [EMAIL PROTECTED] wrote: > What a pity not having sensible packages of djb software in debian (e.g. > see bind's youngest secu

Re: [PROPOSAL] Allowing crypto in the main archive

2001-01-30 Thread Raul Miller
On Tue, Jan 30, 2001 at 09:23:26AM +1000, Anthony Towns wrote: > Personally, I'm developing a bit of a pet peeve against people who > insist that things be done while at the same time refusing to do them > themselves. > > Are you going to go through the distribution and maintain a list of > which p

Re: Source package policy problem.

2001-01-30 Thread pape
On Sun, Jan 28, 2001 at 12:14:58AM -0500, Russell Nelson wrote: > Manoj Srivastava writes: > > >>"pape" == pape <[EMAIL PROTECTED]> writes: > > > > pape> Is it policy conform to have a package (or packages depending on > each > > pape> other) installing binaries in /usr/bin/ _and_ providin