Scribit Paul TBBle Hampson dies 31/03/2007 hora 00:58:
> I'm going to have to have a look at quilt. I was under the impression
> that it was a rather complicated patch-management system, used for
> example by Andrew Morton for managing the -mm tree pre git.
quilt is just a must-know IMHO when you
Scribit Andrew Donnellan dies 31/03/2007 hora 08:31:
> It's the 2-clause BSD license, the 'FreeBSD' license is just the
> 2-clause BSD with FreeBSD names put in.
FreeBSD license
This is the original BSD license with the advertising clause and
another clause removed. (It is also sometimes
Dear mentors,
I am looking for a sponsor for my package "mt19937".
* Package name: mt19937
Version : 1.1-1
Upstream Author : Douglas T. Crosher and Raymond Toy
* URL : http://www.cliki.net/MT19937
* License : Public Domain
Section : libs
It builds th
Scribit Pete Figh dies 01/04/2007 hora 01:58:
> It should be in Debian because there is no other package, that
> provides such funktionality.
I suspect the violence it will be rejected with will be a pretty good
measure of how Debian developers care about their users.
It's an interesting package.
Scribit Michael M. dies 02/04/2007 hora 07:48:
> This sounds great, but could you please advice which brand of popcorn
> meets the DFSG? I wouldn't want to violate the spirit of the
> endeavor.
Probably only the one with traceability information, so you have the
possibility to access the source o
Scribit Bernhard R. Link dies 07/04/2007 hora 16:32:
> - http://newlisp.org from debian/copyright is no URL without a / at
> the end
According to RFC 2396, a generic URI without a path component is a valid
one (section 3). It is very uncommon, though.
Uncommonly,
Pierre
--
[EMAIL PROTECTED]
Open
Scribit Russ Allbery dies 13/04/2007 hora 11:05:
> I've never seen anything that can manage a set of patches as smoothly
> and as intuitively as quilt.
I used quilt before, but now I only use its Mercurial counterpart,
Mercurial queues. Its integration in the VCS makes it easier to use. I
suppose
Among my 5 packages waiting at mentors.d.n, only the two more recents
close ITP bugs. Would it be better practice if I issue a new Debian
revisions for the 3 others after opening an ITP bug, with a changelog
closing the latter?
Curiously,
Pierre
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
signature
Hi,
As an interesting Common Lisp library was published some days ago, I
packaged it with its dependencies that are not yet in Debian. The
library itself is Vecto, a high-level lbrary for vector drawing based on
CL-Vectors (low-level vector drawing) and Salza-PNG (PNG writer), its
other dependenci
Now my five packages close their ITP bug:
vecto - http://bugs.debian.org/444729
cl-vectors - http://bugs.debian.org/444910
salza-png - http://bugs.debian.org/444778
bordeaux-threads - http://bugs.debian.org/444911
mt19937 - http://bugs.debian.org/444912
Documentally,
Pierre
--
[EMAIL PROTECTED]
Scribit Neil Williams dies 02/10/2007 hora 09:57:
> > ITP bugs are not required.
> ITP bugs are required by most sponsors. As DD's, you and I are free to
> skip ITP bugs but maintainers needing sponsorship should file an ITP.
Indeed there's very valuable information layed out in a very friendly
w
> both look sub-optimal to me, could anyone give me advice on this,
> please?
You could just use presint install/upgrade old-version to remove those
directories, if they are empty... See policy 6.5
Quickly,
le Moine Fou
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
pgp8PV6PEVaOH.pgp
Description: PGP
> both look sub-optimal to me, could anyone give me advice on this,
> please?
You could just use presint install/upgrade old-version to remove those
directories, if they are empty... See policy 6.5
Quickly,
le Moine Fou
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
pgp0.pgp
Description: PGP sign
13 matches
Mail list logo
