headers
Thorsten Glaser | 1 Nov 2004 13:44
Picon

certification mark for "mirbsdksh"?

Hello!

It's me again; as discussed in the thread around
Message-ID: <16748.10416.164168.938434@...>
I'm now submitting the first batch of particular licences
used for one of the sub-project spin-offs[1] off the MirOS
project: MirbsdKsh (http://wiki.mirbsd.de/MirbsdKsh).

Most of the code is inherited from pdksh, which was placed
into the public domain by their original authors.

The other licences attached are:

 - the MirOS licence template[2], which I have already
   submitted for fast-track approval after a suggestion
   by John Cowan in
   http://article.gmane.org/gmane.comp.licenses.open-source.general/3332

 - a wording variant of the 2-clause BSD licence:

	Copyright (c) 2002 Marc Espie.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions
	are met:
	1. Redistributions of source code must retain the above copyright
	   notice, this list of conditions and the following disclaimer.
	2. Redistributions in binary form must reproduce the above copyright
	   notice, this list of conditions and the following disclaimer in the
	   documentation and/or other materials provided with the distribution.
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Cowan | 1 Nov 2004 14:09
Favicon

Re: certification mark for "mirbsdksh"?

Thorsten Glaser scripsit:

>  - a wording variant of the 2-clause BSD licence:
> 
> 	Copyright (c) 2002 Marc Espie.
> 
> 	Redistribution and use in source and binary forms, with or without
> 	modification, are permitted provided that the following conditions
> 	are met:
> 	1. Redistributions of source code must retain the above copyright
> 	   notice, this list of conditions and the following disclaimer.
> 	2. Redistributions in binary form must reproduce the above copyright
> 	   notice, this list of conditions and the following disclaimer in the
> 	   documentation and/or other materials provided with the distribution.
> 
> 	THIS SOFTWARE IS PROVIDED BY THE OPENBSD PROJECT AND CONTRIBUTORS
> 	``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> 	LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
> 	A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OPENBSD
> 	PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> 	SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> 	LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> 	DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
> 	THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> 	(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> 	OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This license is obviously Open Source (and Free, and Fair) and should be
fast-tracked by OSI.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thorsten Glaser | 1 Nov 2004 14:26
Picon

Re: certification mark for "mirbsdksh"?

John Cowan dixit:

[...]
>This license is obviously Open Source (and Free, and Fair) and should be
>fast-tracked by OSI.

Okay. Who is the person who can give official statements on these three?
Russel?

[...]
>This is the current BSD license, and is already approved by OSI.

Yes, I thought so, that's why I didn't copy it ;-)

bye,
//mirabile
Permalink | Reply | 0 comments |
headers
R. Tyler Ballance | 3 Nov 2004 15:21
Picon

Re: CVS: loki.66h.42h.de: www

Can you throw a directive in there to not try to send mails to the
cvs-mailing list if the host is not loki?

I keep getting a bunch of failed-to-send messages to root@...
when it syncs those new changes.

Why, I don't know, it just does it.

-R. Tyler Ballance

On Wed, 2004-11-03 at 08:08, Thorsten Glaser wrote:
> CVSROOT:	/cvs
> Module name:	www
> Changes by:	tg@...	2004/11/03 14:08:38 UTC
> 
> Modified files:
> 	.              : .cvsignore 
> 
> Log message:
> add tempidx, for those mirrors which need it
>
Permalink | Reply | 1 comment |
headers
Thorsten Glaser | 3 Nov 2004 15:15
Picon

Re: CVS: loki.66h.42h.de: www

R. Tyler Ballance dixit:

>Can you throw a directive in there to not try to send mails to the
>cvs-mailing list if the host is not loki?
>
>I keep getting a bunch of failed-to-send messages to root@...
>when it syncs those new changes.
>
>Why, I don't know, it just does it.

Looks like you _still_ commit locally. Don't do it.
Think that /cvs/mir is read-only except for the user
who does the rsync. Better, set the Unix permission
bits so that nobody except the rsync owner can write
to it.

Whenever such an error occurs, or - worse - an actual
mail is sent out from any different machine, root has
shoot himself into the foot. (This excludes the case
when, for example on 20C3, odem is the CVS master -
which is also the reason why I haven't added such a
check.)

//mirabile

PS: Please do read http://www.afaik.de/usenet/faq/zitieren/
    10x
Permalink | Reply | 0 comments |
headers
Thorsten Glaser | 3 Nov 2004 19:08
Picon

Re: CVS: loki.66h.42h.de: src

Thorsten Glaser dixit:

>Modified files:
>	usr.bin/patch  : util.c 
>
>Log message:
>merge

This is an important fix. I urge -current users to upgrade
if their patch(1) contains the old code:

tg <at> odem:/home/tg $ what /usr/obj/D/base/usr/bin/patch | fgrep util.c	# broken
        $MirBSD: src/usr.bin/patch/util.c,v 1.2 2004/10/19 18:11:04 tg Exp $

tg <at> odem:/home/tg $ what /usr/bin/patch | fgrep util.c                	# fixed
        $MirBSD: src/usr.bin/patch/util.c,v 1.3 2004/11/03 15:46:16 tg Exp $

If your patch(1) is older, it's not that problematic.

bye,
//mirabile
Permalink | Reply | 0 comments |
headers
Russell Nelson | 3 Nov 2004 20:45
Favicon

Re: certification mark for "mirbsdksh"?

Thorsten Glaser writes:
 > John Cowan dixit:
 > 
 > [...]
 > >This license is obviously Open Source (and Free, and Fair) and should be
 > >fast-tracked by OSI.
 > 
 > Okay. Who is the person who can give official statements on these three?
 > Russel?

Not me alone.  The license has to be submitted according to the steps
given in http://opensource.org/docs/certification_mark.html#approval,
approved by license-discuss (John's comments are obviously helpful
there), and presented to the OSI board for a vote.

If all you've ever done is talk about your license on license-discuss,
it will never be approved.  Not through any animosity, simply because
everyone on the OSI board is a busy person.  We need the structure of
the approval process to make sure that licenses don't get lost.

--

-- 
--My blog is at angry-economist.russnelson.com  | Violence never solves
Crynwr sells support for free software  | PGPok | problems, it just changes
521 Pleasant Valley Rd. | +1 212-202-2318 voice | them into more subtle
Potsdam, NY 13676-3213  | FWD# 404529 via VOIP  | problems.
Permalink | Reply | 0 comments |
headers
Thorsten Glaser | 3 Nov 2004 20:47
Picon

Re: certification mark for "mirbsdksh"?

Russell Nelson dixit:

>If all you've ever done is talk about your license on license-discuss,
>it will never be approved.

What did I miss to do, then?

The website says I have to submit it with "For approval:" prefixed
the Subject: header.

bye,
//mirabile
Permalink | Reply | 0 comments |
headers
Benedikt Steinbusch | 5 Nov 2004 07:03
Picon

Port: www/pear-DB

Hello everyone,

this is my first port for the MirPorts framework. I've done it because 
mira wouldn't have installed it on thor otherwise. It's crap, but it works,
I think. Now mira please install this port on thor and let's all be happy
again with a wonderfull os in a world of peace...

Thanks

--

-- 
Benedikt Steinbusch
Attachment (pear-DB.tar.gz): application/octet-stream, 1752 bytes
Permalink | Reply | 1 comment |
headers
Thorsten Glaser | 5 Nov 2004 09:01
Picon

Re: Port: www/pear-DB

Benedikt Steinbusch dixit:

> this is my first port for the MirPorts framework. I've done it because mira
> wouldn't have installed it on thor otherwise. It's crap, but it works,

No need to not respect yourself. If you think positive,
all will be better.
In fact, I've tried hard to find stuff I can say "not ok"
about in your port and not found anything ;-)

Read the diff between what you sent and what I committed;
it's mostly small style nits, but you might remember it
next time you do a port.

> I think.

Please test the package on thor now.
Congratulations for the maintainership on your first MirPort ;-)

//mirabile
Permalink | Reply | 0 comments |

Gmane