Russ Allbery writes:
> Jonathan Nieder writes:
>
>> How about this?
>
>> diff --git i/policy.sgml w/policy.sgml
>> index 7d514921..58bde0bb 100644
>> --- i/policy.sgml
>> +++ w/policy.sgml
>> @@ -3766,8 +3766,9 @@ Checksums-Sha256:
>>
>>The field name identifies the
Frans Pop writes:
> Inclusion of this command should not pose any problems as it has been
> supported since 1993 (debconf version 1.3.22).
I think you mean 2003.
Otherwise looks fine to me. Seconded.
--
Ben Pfaff
http://benpfaff.org
--
To UNSUBSCRIBE, email to debian-polic
er/
>>
>> to disambiguate the calculation.
>
> Does du guarantee to do one of those?
The specification at
http://www.opengroup.org/onlinepubs/009695399/utilities/du.html says:
By default, file sizes shall be written in 512-byte units,
rounded up to the next 512-byte un
rement being applied uniformly? I don't see any
such attempt in linux-image-2.6.28-1-686, to pick one example at
random, even though the Linux kernel comes with a very long list
of subsystem maintainers who are presumably authors or copyright
holders.
--
Ben Pfaff
http://benpfaff.org
--
To UNSU
der the GNU GPL, just as the rest
> - of dpkg is.)
> -
> -
> -
>
> +
>
> Copyright: debian/copyright
>
Seconded. (The support for alternative changelog formats always
seemed bizarre to me, and I never saw the motivation for it.)
--
Ben Pfaff
http://benpfaff.org
pgpdWgX0PBgaV.pgp
Description: PGP signature
my opinion, and it's a perfectly good
free software license, so I am in favor of adding the Apache 2.0
license to the list of common-licenses.
--
Ben Pfaff
http://benpfaff.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
efinitely
> have seen issues. And the Autoconf 2.13 to 2.50 transition and all the
> subsequent instability was not that long ago.
Autoconf 2.50 was released in May 2001. That's almost 7 years
ago now. By free software release standards, I would not
consider that "not that long ago&quo
Russ Allbery <[EMAIL PROTECTED]> writes:
> +
> + The URL of the web site for this package, preferrably (when
Nit: preferrably -> preferably
--
"Writing is easy.
All you do is sit in front of a typewriter and open a vein."
--Walter Smith
--
To UNSUBSCRIBE, email to [EMAIL PROTE
Anthony Towns <[EMAIL PROTECTED]> writes:
> On Thu, Dec 06, 2007 at 05:09:36PM -0600, Manoj Srivastava wrote:
>> On Thu, 06 Dec 2007 13:34:10 -0800, Ben Pfaff <[EMAIL PROTECTED]> said:
>> > I use "time" in benchmarking scripts.
>> I do not
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> On Thu, 06 Dec 2007 13:34:10 -0800, Ben Pfaff <[EMAIL PROTECTED]> said:
>
>> I use "time" in benchmarking scripts.
>
> I do not find the built in time to be a substitute for the good
> old f
time is only used in interactive shells, so this might not be
> that important. IMHO it could be relegated to optional.
I use "time" in benchmarking scripts.
--
Ben Pfaff
http://benpfaff.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Russ Allbery <[EMAIL PROTECTED]> writes:
> Bill Allombert <[EMAIL PROTECTED]> writes:
>
>> I find the wording "convenience copy of library from other software
>> packages" much more telling than "convenience copy of code from other
>> software packages" that could be misinterpreted. For example, a
Massimo Dal Zotto <[EMAIL PROTECTED]> writes:
> I wrote an automatic installer (which worked) for slink, but I had to
> spend weeks to adapt the postinst scripts of debian packages to it,
> and I didn't want to repeat all the work for potato and woody.
This was my experience, too.
> In my opinio
Franklin Belew <[EMAIL PROTECTED]> writes:
> PS: I know my lines are longer than 76 characters, fix your own pager/viewers
> wordwrap
No, fix your attitude and read RFC1855. Excerpt:
- Limit line length to fewer than 65 characters and end a line
with a carriage return.
One wrong assumption I keep seeing in this thread is that if you can
read a format, then you can write it. That's simply not true. You
may not have enough information.
For instance, suppose that a file format contains a checksum, with the
calculation of the checksum undocumented. In that case,
Ben Gertzfield <[EMAIL PROTECTED]> writes:
>>>>> "Ben" == Ben Pfaff <[EMAIL PROTECTED]> writes:
Tom> This sounds very useful! Are we going to package it somehow?
Ben> The problem is that one of the license requirements (3c (?))
[EMAIL PROTECTED] (Karl M. Hegbloom) writes:
> "Manoj" == Manoj Srivastava <[EMAIL PROTECTED]> writes:
Manoj> Hi
>>> "Karl" == Karl M Hegbloom <[EMAIL PROTECTED]> writes:
Karl> Also, "ChangeLog" files are named with capital `C' and `L'
Karl> when you use `C-x 4
Guy Maor <[EMAIL PROTECTED]> writes:
Zed Pobre <[EMAIL PROTECTED]> writes:
> As a sidenote, if anyone has an idea for templates for proposals, or
> a format that would make proposals more readable or in some other
> manner more aesthetic or easier to deal with than what I posted,
I think that this proposed policy is too strict. It forbids several
commands already in widespread use on the system, and it forbids
program names from being a single (English?) word, which is
unreasonable, in my opinion.
Some command names that this policy forbids:
(Section 1) GnomeScott Mail M
[I'm CC'ing this to debian-policy because I think it's an important
general issue.]
What I think it would be best is to tell the user that Samba was
previously installed and ask if he/she wants to keep the current
configuration (regarding running mode). What do you think? I think
sever
[...example text for /etc/init.d/README...]
The Debian Policy Manual is ofcourse also available as a debian package.
I suggest being more specific here. Something like:
The Debian Policy Manual is also available in the Debian package
`debian-policy'. When this package is installed, t
> Furthermore, commas are no good because they're already a separator
> for separate addresses in a single field. (Admittedly we already
> allow a syntax like John F. Bloggs <[EMAIL PROTECTED]> which is not
> permitted by RFC822.)
Why?
'John F. Bloggs <[EMAIL PROTECTED]>' s
- change the current DB schema to be able to store different
"Maintainer:" email addresses for each person
This is the best solution IMHO. It is more flexible and doesn't force
adoption of a single e-mail address. Although I myself only use a
single address, I respect the reasons of p
If bash is invoked with the name sh, it tries to mimic the
startup behavior of historical versions of sh as closely
as possible, while conforming to the POSIX standard as
well.
So, if POSIX says that the example above should be
$ echo hello {the
ytes.
Why is it a bad thing in itself to have more packages, even if we have
a lot of them?
--
Ben Pfaff <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Rob Browning <[EMAIL PROTECTED]> writes:
> 1) Create two packages: foo and foo-tk
I can't see any real downsides to this. If `foo' suggests `foo-tk'
(and `foo-tk' depends on `foo'), then we've got the best of both
worlds.
--
Ben Pfaff <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
that we do it.
Won't our turning off --force-overwrite in 2.0 be a more realistic
solution of this problem? Aren't most package conflicts really
related to their usage of competing file structures? Or am I totally
off-base here?
--
Ben Pfaff <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
(from 2.7.2.3) stay on master, at least until a newer
Checker is released?
--
Ben Pfaff <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Senders of unsolicited commercial e-mail will receive free 32MB core files!
appy not to be proved wrong on that score.
Hmmm... Looking through the policy manual, I can't see such a
requirement either. But what is the proper way to specify in the
source package that additional sources are needed? And where should
they go?
--
Ben Pfaff <[EMAIL PROTECTED]> <[EMAIL PRO
Guy Maor <[EMAIL PROTECTED]> writes:
> Ben Pfaff <[EMAIL PROTECTED]> writes:
>
> > In my opinion, this is an unreasonable amount of source code to
> > include in a source package, since all the source code is available
> > elsewhere. However, Debian policy
think that Debian policy should be modified, in some way, to allow a
situation like this to exist and to specify some standard place that
the tarballs can be provided. For instance, Checker expects the
tarballs in a directory called ../tarballs.
Comments?
--
Ben Pfaff <[EMAIL PROTECTED]> &
in the packaging before passing it on to upstream
authors.
--
Ben Pfaff <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Senders of unsolicited commercial e-mail will receive free 32MB core files!
library. I notice that on my system the
> libraries and binaries in the anonymous FTP chroot directory are
> older than the rest of the system.
You could use proftpd, which doesn't require these utilities in the
anonftp directory.
--
Ben Pfaff <[EMAIL PROTECTED]> <[EMAIL PROTE
only if I write a tool to edit the lines,
> don't try to edit them directly...)
Just FYI, in case you didn't know: GNU emacs 20.x includes a
(optional) set of international fonts for X11. *Lots* of them. In
*many* languages. You might want to consider this.
--
Ben Pfaff <[E
34 matches
Mail list logo
