From daniel at danm.de  Tue Mar  1 22:47:15 2005
From: daniel at danm.de (Daniel Mueller)
Date: Tue, 1 Mar 2005 23:47:15 +0100
Subject: [clc-devel] Email format in Pkgfile
In-Reply-To: <419865F0.60508@varlock.com>
References: <20041113184833.091c8255@torax.home.danm.de>
	<419865F0.60508@varlock.com>
Message-ID: <20050301234715.2cc2816d@torax.home.danm.de>

On Mon, 15 Nov 2004 09:16:48 +0100
Simone Rota wrote:

> Yes. This is definitely a problem for me.
> The spam amount I get at my varlock.com address passed
> from 'near to zero' to 'way too much' since I've been
> using it in Pkgfiles.

Johannes suggested these formats:

@ = % and . = * 

jew%tks69*net
jew % tks69 * net
jew%tks69.net

Matti Kraft <joghurt % morpheus.net>
Jean Wolfman, jew % tks69.net

Any other ideas, comments?

bye, danm

-- 
Daniel Mueller          http://www.danm.de
Berlin, Germany         OpenPGP: 1024D/E4F4383A


From jw at tks6.net  Wed Mar  2 19:22:53 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Wed, 2 Mar 2005 20:22:53 +0100
Subject: [clc-devel] Application for CLC Maintainer
In-Reply-To: <421D25C3.5060200@yahoo.de>
References: <421D25C3.5060200@yahoo.de>
Message-ID: <20050302192253.GA3262@narvik.tks6.lan>

On Thu, Feb 24, 2005 at 01:54:27 +0100, Till Biedermann wrote:
> Hi everybody,
> 
> when Johannes ask me to maintain a wiki page about my freevo ports I 
> started (once again) thinking about an application to become a CLC 
> maintainer.
As far as I can tell we're all happy about your application, and would
like to welcome you at CLC. I've also talked with Till about moving his
MySQL ports database to CLC, since we might try to reintroduce some
statistics (lastest added/changed ports etc.) around the ports tree(s).

Matt, can you create an account for him?
Kind regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From sip at varlock.com  Fri Mar  4 13:35:32 2005
From: sip at varlock.com (Simone Rota)
Date: Fri, 04 Mar 2005 14:35:32 +0100
Subject: [clc-devel] Email format in Pkgfile
In-Reply-To: <20050301234715.2cc2816d@torax.home.danm.de>
References: <20041113184833.091c8255@torax.home.danm.de>	<419865F0.60508@varlock.com> <20050301234715.2cc2816d@torax.home.danm.de>
Message-ID: <42286424.7050105@varlock.com>

On 03/01/05 23:47 Daniel Mueller wrote:
> 
> Johannes suggested these formats:
> 
> @ = % and . = * 
> 
> jew%tks69*net
> jew % tks69 * net
> jew%tks69.net
> 
> Matti Kraft <joghurt % morpheus.net>
> Jean Wolfman, jew % tks69.net
> 
> Any other ideas, comments?

Matti Kraft, joghurt % morpheus * net

is my favourite, but as i wrote before I'm afraid
any recent email harvester app would spot an email
address anyway.

maybe

Matti Kraft, joghurt morpheus net

is a little more subtle.

Anyway, I think we should agree on some common format
before 2.1, so we can avoid some cvs noise just for
email adjustements

Regards,
Simone


-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From jw at tks6.net  Sat Mar  5 12:43:57 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Sat, 5 Mar 2005 13:43:57 +0100
Subject: [clc-devel] Request for comments: subversion repository
Message-ID: <20050305124357.GA6214@narvik.tks6.lan>

Hi there,
As some of you might remember, I posted a proposal how to use subversion
for port maintenance:
  https://lists.berlios.de/pipermail/clc-devel/2004-December/000730.html

I was thinking about setting up a subversion ports repo at berlios
(since the clc project already has a subversion repository there), but
I'd like to check first whether there's any interest from other people.
So please let me know whether you're interested in testing it.

For those wondering about the reasons for this, here we go:
- subversion has some advantages over CVS, which make it easier to work
  with (e.g. disconnected add/diff/revert)
- subversion repositories can be published over http, which would solve
  the firewalling problem several people have with cvsup
- several tools exist for distributed development (svk, submaster) or
  patch management (transsvn)

As an addition, the script I wrote would allow to maintain "slave"-ports
on other architectures, where changes from a main architecture can be
merged as wanted.

If there's any substantial interest, I'd volunteer to initialize the
repository for x86, sparc and $TESTARCH (to allow everyone playing with
multiple architectures).

Kind regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From sip at varlock.com  Sat Mar  5 21:26:40 2005
From: sip at varlock.com (Simone Rota)
Date: Sat, 5 Mar 2005 21:26:40 +0000 (UTC)
Subject: [clc-devel] Request for comments: subversion repository
In-Reply-To: <20050305124357.GA6214@narvik.tks6.lan>
References: <20050305124357.GA6214@narvik.tks6.lan>
Message-ID: <Pine.LNX.4.62.0503052052170.1007@ucrux>

On Sat, 5 Mar 2005, Johannes Winkelmann wrote:

> I was thinking about setting up a subversion ports repo at berlios
> (since the clc project already has a subversion repository there), but
> I'd like to check first whether there's any interest from other people.
> So please let me know whether you're interested in testing it.
>
> If there's any substantial interest, I'd volunteer to initialize the
> repository for x86, sparc and $TESTARCH (to allow everyone playing with
> multiple architectures).

I'm interested in working on a uClibc tree; while not strictly a different
arch, 20% of ports need some patch against the glibc counterparts, so
it could be an interesting testbed.
(providing svn compiles and works on uclibc, never tried so far)

In the future I'd like to have some work on a AMD64 port as well.

What about base and opt ports? Will they be included in the SVN repo?
I'm still a bit confused about the new port tree layout for CRUX+CLC

In general, I think it would be a good idea to make the point of what's
going on regarding CRUX 2.1, but this really belongs to another thread.

Regards,
Simone


From tilman at code-monkey.de  Sun Mar  6 11:47:09 2005
From: tilman at code-monkey.de (Tilman Sauerbeck)
Date: Sun, 6 Mar 2005 12:47:09 +0100
Subject: [clc-devel] Request for comments: subversion repository
In-Reply-To: <20050305124357.GA6214@narvik.tks6.lan>
References: <20050305124357.GA6214@narvik.tks6.lan>
Message-ID: <20050306114709.GA7666@code-monkey.de>

Johannes Winkelmann <jw at tks6.net> [2005-03-05 13:43]:
> I was thinking about setting up a subversion ports repo at berlios
> (since the clc project already has a subversion repository there), but
> I'd like to check first whether there's any interest from other people.
> So please let me know whether you're interested in testing it.

I'd happily help testing, too :)

-- 
Regards,
Tilman


From jaeger at morpheus.net  Mon Mar  7 14:24:38 2005
From: jaeger at morpheus.net (Matt Housh)
Date: Mon, 07 Mar 2005 08:24:38 -0600
Subject: [clc-devel] Request for comments: subversion repository
In-Reply-To: <20050305124357.GA6214@narvik.tks6.lan>
References: <20050305124357.GA6214@narvik.tks6.lan>
Message-ID: <1110205478.17851.0.camel@charon.frc.utulsa.edu>

I've always liked the idea of trying svn for ports, I'm all for a test
at the least. I use it for my personal stuff and love it.

Matt (jaeger at freenode/#crux)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20050307/56082d86/attachment.asc>

From jw at tks6.net  Mon Mar  7 18:47:50 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 7 Mar 2005 19:47:50 +0100
Subject: [clc-devel] Request for comments: subversion repository
In-Reply-To: <Pine.LNX.4.62.0503052052170.1007@ucrux>
References: <20050305124357.GA6214@narvik.tks6.lan> <Pine.LNX.4.62.0503052052170.1007@ucrux>
Message-ID: <20050307184750.GE6214@narvik.tks6.lan>

Hey Simone,

On Sat, Mar 05, 2005 at 21:26:40 +0000, Simone Rota wrote:
> On Sat, 5 Mar 2005, Johannes Winkelmann wrote:
[...]
> >If there's any substantial interest, I'd volunteer to initialize the
> >repository for x86, sparc and $TESTARCH (to allow everyone playing with
> >multiple architectures).
> 
> I'm interested in working on a uClibc tree; while not strictly a different
> arch, 20% of ports need some patch against the glibc counterparts, so
> it could be an interesting testbed.
> (providing svn compiles and works on uclibc, never tried so far)
> 
> In the future I'd like to have some work on a AMD64 port as well.
Both of them are very good examples where the subversion setup _might_
save some work.

> What about base and opt ports? Will they be included in the SVN repo?
> I'm still a bit confused about the new port tree layout for CRUX+CLC
Right, this is a good remark; in order to be helpful for the SPARC port,
base and opt(+contrib) should be there; it would be best if we could
sync the clc tree automatically, I'm not sure yet if this can be done
easily.

Otherwise, it would just be a test run, in which case I think it would
be easiest to use only a few ports.

> In general, I think it would be a good idea to make the point of what's
> going on regarding CRUX 2.1, but this really belongs to another thread.
I agree, but in order to discuss this seriously, some experience would
be good; if it works out as good as CVS or better, we can certainly
consider the switch.


As a (rather interesting) sidenote:

I'm not yet sure about the use cases we have, and how well xsvn copes
with that; imagine the following:

3-arch setup, x86, x86_64, sparc:

1. a port is added to x86
2. both x86_64 and sparc ports are synced (merged from x86)

Now, if the x86 port is updates, sparc and x86_64 can merge nicely,
since xsvn set the revision number where it merged from. It's a bit
different when the x86_64 maintainer is faster, and the x86 person would
like to merge those changes; since we didn't store the branch point from
x86 to x86_64, we could only try to be smart (I'm thinking about that
right now...).

I was wondering whether it would be okay to always require version
numbers for cross-platform merges; imagine the above situation, where
the x86_64 maintainer was faster with an update, and the x86 maintainer
would just like to get those changes, too; in this case, the x86
maintainer would have to find out the revision number of the change
(e.g. in the timeline, or via commit notification), and do something
like
 xsvn merge-from sparc64 port -r 100
or if one would want to merge multiple changes, to an
 xsvn merge-from sparc64 port -r 100,101,102

Not sure if I'm clear here, but implementing a merge tracking which
works bidirectional by means of svn properties is certainly not an easy
task... and the explicit selection doesn't look all bad to me, since I'd
expect that if we would do a simple "merge all that was changed since
the last merge", we'd get some unecessary changes. Opinions, questions?

Kind regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jw at tks6.net  Mon Mar  7 20:30:35 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 7 Mar 2005 21:30:35 +0100
Subject: [clc-devel] Request for comments: subversion repository
In-Reply-To: <20050305124357.GA6214@narvik.tks6.lan>
References: <20050305124357.GA6214@narvik.tks6.lan>
Message-ID: <20050307203035.GF6214@narvik.tks6.lan>

Hi,

I added some folders to the repository:
  http://svn.berlios.de/viewcvs/clc/

Have a look at the following document to learn how to check out files:
  https://developer.berlios.de/svn/?group_id=847

Unfortunately, berlios doesn't offer subversion over http, but IMHO
this is a minor problem at the moment.

At the risk of making this another boring mail (danm ;-)), here comes
the log of my commits (after creating the initial structure):

Please ask if you'd like to learn more!


##
# first: add a single port to x86
mkdir /tmp/single-arch
cd /tmp/single-arch
svn co svn+ssh://svn.berlios.de/svnroot/repos/clc/x86/trunk
cd trunk
cp -r ~/crux/clc/htop .
svn add -N htop
cd htop
svn add Pkgfile .footprint .md5sum
svn ci -m "initial commit of htop"
-> http://svn.berlios.de/viewcvs/clc/x86/trunk/

##
# second: merge it to sparc
export XSVN_SRC_REPO=svn+ssh://svn.berlios.de/svnroot/repos/clc/x86 
export XSVN_BASE_REPO=svn+ssh://svn.berlios.de/svnroot/repos/clc/sparc
export XSVN_RELEASE=CRUX-2_0

mkdir /tmp/work-multi
cd /tmp/work-multi
svn co $XSVN_BASE_REPO/trunk
cd trunk

xsvn merge-from htop
svn ci -m "commit htop to sparc"
-> http://svn.berlios.de/viewcvs/clc/sparc/trunk/


## 
# release it to base of sparc 2.0
xsvn release base htop
[ editor pops up; say "add htop to sparc/2.0" ]
-> http://svn.berlios.de/viewcvs/clc/sparc/tags/CRUX-2_0/base/


##
# release htop to x86 2.0
export XSVN_BASE_REPO=svn+ssh://svn.berlios.de/svnroot/repos/clc/x86
xsvn release base htop
-> http://svn.berlios.de/viewcvs/clc/x86/tags/CRUX-2_0/base/


##
# merging to x86_64
export XSVN_BASE_REPO=svn+ssh://svn.berlios.de/svnroot/repos/clc/x86_64
mkdir /tmp/work-multi-64
cd /tmp/work-multi-64
svn co $XSVN_BASE_REPO/trunk
cd trunk
xsvn merge-from htop
svn ci -m "commit htop to x86_64"
-> http://svn.berlios.de/viewcvs/clc/x86_64/trunk/

##
# and finally release htop to x86_64 2.0; opt this time
xsvn release opt htop
-> http://svn.berlios.de/viewcvs/clc/x86_64/tags/CRUX-2_0/opt/


##
# add it to x86_64, crux 2.1:
export XSVN_RELEASE=CRUX-2_1
xsvn release opt htop



That's it. xsvn is available at 
  http://jw.tks6.net/files/crux/xsvn/xsvn
make sure you're using 0.3 or higher (uploaded five minutes ago).


Enjoy, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From sip at varlock.com  Mon Mar  7 22:15:53 2005
From: sip at varlock.com (Simone Rota)
Date: Mon, 07 Mar 2005 23:15:53 +0100
Subject: [clc-devel] Request for comments: subversion repository
In-Reply-To: <20050307184750.GE6214@narvik.tks6.lan>
References: <20050305124357.GA6214@narvik.tks6.lan> <Pine.LNX.4.62.0503052052170.1007@ucrux> <20050307184750.GE6214@narvik.tks6.lan>
Message-ID: <422CD299.8030207@varlock.com>

On 03/07/05 19:47 Johannes Winkelmann wrote:
>>What about base and opt ports? Will they be included in the SVN repo?
>>I'm still a bit confused about the new port tree layout for CRUX+CLC
> 
> Right, this is a good remark; in order to be helpful for the SPARC port,
> base and opt(+contrib) should be there; it would be best if we could
> sync the clc tree automatically, I'm not sure yet if this can be done
> easily.

Expecially considering that the current uCRUX has only
around 10 contrib ports :)

> Now, if the x86 port is updates, sparc and x86_64 can merge nicely,
> since xsvn set the revision number where it merged from. It's a bit
> different when the x86_64 maintainer is faster, and the x86 person would
> like to merge those changes; since we didn't store the branch point from
> x86 to x86_64, we could only try to be smart (I'm thinking about that
> right now...).
[cut]
> Not sure if I'm clear here, but implementing a merge tracking which
> works bidirectional by means of svn properties is certainly not an easy
> task... and the explicit selection doesn't look all bad to me, since I'd
> expect that if we would do a simple "merge all that was changed since
> the last merge", we'd get some unecessary changes. Opinions, questions?

My view: I think it's a bit dangerous (and complicated as you note)
to let the different archs diverge too much or pump the
updates to the x86 tree.
Maybe it's the case of considering the x86 as the 'main' repository
and keep the other architectures as in sync as possible
with that, since:
- x86 at the moment has more contributors
- more users as well ==> a bit more tested

Eventually the $ARCH maintainer can submit a port
update for x86 to the respective maintainer if there are
significant changes that are not yet in the x86 tree.

Just some random thought, since we don't really have any
idea at the moment about how a multi-platform CRUX
community would evolve when there is an infrastructure
to support it.

So for now I'd opt for the easy, unidirectional way
as presented above.

Regards,
Simone

-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From jw at tks6.net  Tue Mar  8 07:24:10 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Tue, 8 Mar 2005 08:24:10 +0100
Subject: [clc-devel] Application for CLC Maintainer
In-Reply-To: <421D25C3.5060200@yahoo.de>
References: <421D25C3.5060200@yahoo.de>
Message-ID: <20050308072410.GG6214@narvik.tks6.lan>

Hi Till,

I saw you started committing to the CLC CVS, hope you had a good start!
BTW, don't forget to add yourself on 
  http://clc.morpheus.net:6999/clc/wiki?p=AboutClc

Kind regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From jaeger at morpheus.net  Tue Mar  8 16:30:08 2005
From: jaeger at morpheus.net (Matt Housh)
Date: Tue, 08 Mar 2005 10:30:08 -0600
Subject: [clc-devel] CLC Downtime
Message-ID: <1110299408.11527.1.camel@charon.frc.utulsa.edu>

I apologize for the lack of notice, everyone, but I was just informed
our power will be turned off in a few minutes and there's no indication
whatsoever of how long it will be down. I'll have CLC back up as soon as
I can.

Matt (jaeger at freenode/#crux)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20050308/70ae3d54/attachment.asc>

From jaeger at morpheus.net  Tue Mar  8 20:12:04 2005
From: jaeger at morpheus.net (Matt Housh)
Date: Tue, 08 Mar 2005 14:12:04 -0600
Subject: [clc-devel] CLC is back up
Message-ID: <1110312724.1833.0.camel@charon.frc.utulsa.edu>

CLC is back up for those who haven't checked it already.

Matt (jaeger at freenode/#crux)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20050308/ec52eba8/attachment.asc>

From jw at tks6.net  Tue Mar  8 21:36:45 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Tue, 8 Mar 2005 22:36:45 +0100
Subject: [clc-devel] e-mail format in Pkgfiles
Message-ID: <20050308213645.GK6214@narvik.tks6.lan>

Hi,

We've decided to change to e-mail addresses in the Pkgfiles from 
  Joe User <user at domain.com>
  Joe User <user.name at sub.domain.com>
to 
  Joe User, user at domain dot com
  Joe User, user dot name at sub dot domain dot com

The package guidelines have been changed to reflect this:
  http://clc.morpheus.net:6999/clc/wiki?p=PackageGuidelines

Remember that you can do those changes in a single commit, to keep the
timeline nice and clear ;-)

Kind regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From mo at obbl-net.de  Tue Mar  8 22:37:40 2005
From: mo at obbl-net.de (Opel Martin)
Date: Tue, 08 Mar 2005 23:37:40 +0100
Subject: [clc-devel] e-mail format in Pkgfiles
In-Reply-To: <20050308213645.GK6214@narvik.tks6.lan>
References: <20050308213645.GK6214@narvik.tks6.lan>
Message-ID: <422E2934.3040405@obbl-net.de>

Johannes Winkelmann schrieb:

>Hi,
>  
>
Hi Johannes, hi maintainers,

>We've decided to change to e-mail addresses in the Pkgfiles from 
>  Joe User <user at domain.com>
>  Joe User <user.name at sub.domain.com>
>to 
>  Joe User, user at domain dot com
>  Joe User, user dot name at sub dot domain dot com
>
>The package guidelines have been changed to reflect this:
>  http://clc.morpheus.net:6999/clc/wiki?p=PackageGuidelines
>
>Remember that you can do those changes in a single commit, to keep the
>timeline nice and clear ;-)
>  
>
This sed should do that automatically:

ls */Pkgfile | \
  xargs -n 1 sed -i \
  -e 's/# Maintainer: \(.*\) <\(.*\)@\(.*\)>/# Maintainer: \1, \2 at \3/'
  -e 's/\(# Maintainer: .*\)\.\(.*\)/\1 dot \2/g'

:-)

Please test it first for your ports without the -i option. A second call 
with Packager: instead of Maintainer should change that occurences, too.

>Kind regards, Johannes
>  
>
Bye
Martin.


From mo at obbl-net.de  Tue Mar  8 22:52:39 2005
From: mo at obbl-net.de (Opel Martin)
Date: Tue, 08 Mar 2005 23:52:39 +0100
Subject: [clc-devel] e-mail format in Pkgfiles
In-Reply-To: <422E2934.3040405@obbl-net.de>
References: <20050308213645.GK6214@narvik.tks6.lan> <422E2934.3040405@obbl-net.de>
Message-ID: <422E2CB7.3060401@obbl-net.de>

Opel Martin schrieb:
[...]

> This sed should do that automatically:
>
> ls */Pkgfile | \
>  xargs -n 1 sed -i \
>  -e 's/# Maintainer: \(.*\) <\(.*\)@\(.*\)>/# Maintainer: \1, \2 at \3/'
>  -e 's/\(# Maintainer: .*\)\.\(.*\)/\1 dot \2/g'

The hack was too dirty. The second -e does only replace one '.' :(



From Nick.Steeves at shaw.ca  Wed Mar  9 07:44:17 2005
From: Nick.Steeves at shaw.ca (Nick Steeves)
Date: Wed, 09 Mar 2005 00:44:17 -0700
Subject: [clc-devel] e-mail format in Pkgfiles
In-Reply-To: <20050308213645.GK6214@narvik.tks6.lan>
References: <20050308213645.GK6214@narvik.tks6.lan>
Message-ID: <200503090044.17420.sten@digitalmercury.lb.shawcable.net>

On March 8, 2005 2:36, Johannes Winkelmann wrote:
> Remember that you can do those changes in a single commit, to keep the
> timeline nice and clear ;-)

Can I modify ports where I am packager, but not maintainer?  Also, is there a 
way to re-tag all these modified Pkgfiles in one fell swoop?

Cheers,
Nick


From jw at tks6.net  Sat Mar 12 16:03:34 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Sat, 12 Mar 2005 17:03:34 +0100
Subject: [clc-devel] the new contrib
Message-ID: <20050312160334.GC715@narvik.tks6.lan>

Hi,

I've added a few additional features to Jay's script to merge the httpup
repos for our new 'contrib' collection. It's available at 
  http://jw.tks6.net/files/crux/prtsync-jw/

I did some testing today, and am pretty happy with it. The next logical
step would be to do an testing with some interested repo maintainers,
but there's one question I think we should discuss first: on IRC we've
come to the conclusion that it might be a good idea to explicitely
select ports in your httpup repository which should be considered for
'contrib'. We realized this using a tag file, called '.sync'. So in
order to publish $port, you just do a 'touch $port/.sync &&
httpup-repgen'. This means that if you subscribe to an httpup repository
directly, you'll get .sync files during a ports -u. I think I can live
with that for now, and am confident that if that's a problem, we'll find
a solution. Still I'd like to hear opinions on that.

If there are no objections, let's start testing ASAP. Should we spam
clc-devel with notifications, or use a dedicated list?

Kind regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From sip at varlock.com  Sat Mar 12 17:14:34 2005
From: sip at varlock.com (Simone Rota)
Date: Sat, 12 Mar 2005 18:14:34 +0100
Subject: [clc-devel] the new contrib
In-Reply-To: <20050312160334.GC715@narvik.tks6.lan>
References: <20050312160334.GC715@narvik.tks6.lan>
Message-ID: <4233237A.5050802@varlock.com>

On 03/12/05 17:03 Johannes Winkelmann wrote:
> I've added a few additional features to Jay's script to merge the httpup
> repos for our new 'contrib' collection. It's available at 
>   http://jw.tks6.net/files/crux/prtsync-jw/
> 
> I did some testing today, and am pretty happy with it. The next logical
> step would be to do an testing with some interested repo maintainers,

We could as well temporarily 'adopt' some 3rd party repo,
one for each clc member interested in testing, and test
them internally. This could bring to quicker response times
and/or better understanding of potential issues.
Just an idea, I'm also fine with recruiting some victim, ahem,
volunteer within httpup repo maintainers

> but there's one question I think we should discuss first: on IRC we've
> come to the conclusion that it might be a good idea to explicitely
> select ports in your httpup repository which should be considered for
> 'contrib'. We realized this using a tag file, called '.sync'. So in
> order to publish $port, you just do a 'touch $port/.sync &&
> httpup-repgen'. This means that if you subscribe to an httpup repository
> directly, you'll get .sync files during a ports -u. I think I can live
> with that for now, and am confident that if that's a problem, we'll find
> a solution. Still I'd like to hear opinions on that.

If I understand well this is a way of excluding stuff you
don't want to publish: temp or custom ports, dups, etc.
Ideally I'd prefer to avoid (if possible) ad-hoc solutions
that would differentiate a standard port from a CLC / CRUX
one, but I have no idea on how to treat this issue (apart
from separating the public and custom repository, but this
is surely a pain for the contributor).

> If there are no objections, let's start testing ASAP. Should we spam
> clc-devel with notifications, or use a dedicated list?

I think a new list, specifically for the new contrib members
would be a good idea and a perfect place for these initial tests.

Regards,
Simone

-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From crux at morpheus.net  Sat Mar 12 19:30:30 2005
From: crux at morpheus.net (crux at morpheus.net)
Date: Sat, 12 Mar 2005 13:30:30 -0600
Subject: [clc-devel] [CLC Ticket Notification] PCI: cache line size of 128 is not supported
Message-ID: <20050312193033.4CB3D2C6B0A@dream.morpheus.net>

Assigned to [clc-devel at lists.berlios.de]

The following CLC ticket (65) has been created or modified:

Description:



Remarks:



Contact: jukka dot hellen at gmail dot com
CLC User: anonymous
Status: new

URL:
	http://clc.morpheus.net:6999/clc/tktview?tn=65



From crux at morpheus.net  Sun Mar 13 13:11:20 2005
From: crux at morpheus.net (crux at morpheus.net)
Date: Sun, 13 Mar 2005 07:11:20 -0600
Subject: [clc-devel] [CLC Ticket Notification] PCI: cache line size of 128 is not supported
Message-ID: <20050313131123.552C52C8EA5@dream.morpheus.net>

Assigned to [clc-devel at lists.berlios.de]

The following CLC ticket (65) has been created or modified:

Description:



Remarks:



Contact: jukka dot hellen at gmail dot com
CLC User: jw
Status: closed

URL:
	http://clc.morpheus.net:6999/clc/tktview?tn=65



From jw at tks6.net  Sun Mar 13 17:42:20 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Sun, 13 Mar 2005 18:42:20 +0100
Subject: [clc-devel] e-mail format in Pkgfiles
In-Reply-To: <200503090044.17420.sten@digitalmercury.lb.shawcable.net>
References: <20050308213645.GK6214@narvik.tks6.lan> <200503090044.17420.sten@digitalmercury.lb.shawcable.net>
Message-ID: <20050313174220.GD715@narvik.tks6.lan>

Hi,

On Wed, Mar 09, 2005 at 00:44:17 -0700, Nick Steeves wrote:
> On March 8, 2005 2:36, Johannes Winkelmann wrote:
> > Remember that you can do those changes in a single commit, to keep the
> > timeline nice and clear ;-)
> 
> Can I modify ports where I am packager, but not maintainer?  Also, is there a 
> way to re-tag all these modified Pkgfiles in one fell swoop?
I think you already changed your ports, but just for the records (or
those who haven't changed their ports yet): it's certainly just fine to
update ports where you're just the packager (just update the maintainer
field as well). 

Regarding cvs, just do 
  cvs commit port1 port2 port3
followed by a
  cvs tag -F CONTRIB-2_0 port1 port2 port3
from the base directory of your cvs checkout.

HTH, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From sip at varlock.com  Fri Mar 18 11:01:28 2005
From: sip at varlock.com (Simone Rota)
Date: Fri, 18 Mar 2005 12:01:28 +0100
Subject: [clc-devel] dropping xmms
Message-ID: <423AB508.8000507@varlock.com>

Hi there,

I'm testing bmp[1] on a couple of machines and it seems
quite stable, so I'll probably drop xmms maintainership
in a few days.

If somebody wants to take care of it (and related ports),
please feel free to do so.

Regards,
Simone

[1] http://beepmp.sourceforge.net/

-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com


From blizz at evilhackerdu.de  Sun Mar 27 10:36:24 2005
From: blizz at evilhackerdu.de (Stephan Seidt)
Date: Sun, 27 Mar 2005 12:36:24 +0200
Subject: [clc-devel] dropping xmms
In-Reply-To: <423AB508.8000507@varlock.com>
References: <423AB508.8000507@varlock.com>
Message-ID: <42468CA8.1060503@evilhackerdu.de>

Hi,

I can only confirm that. BMP became very stable. :)
And it looks like it's still in development
(there was some BMP2 draft somewhere with a whole new API or something, 
can't remember).

Regards,
stephan

Simone Rota wrote:
> Hi there,
> 
> I'm testing bmp[1] on a couple of machines and it seems
> quite stable, so I'll probably drop xmms maintainership
> in a few days.
> 
> If somebody wants to take care of it (and related ports),
> please feel free to do so.
> 
> Regards,
> Simone
> 
> [1] http://beepmp.sourceforge.net/
> 



From crux at morpheus.net  Mon Mar 28 16:52:56 2005
From: crux at morpheus.net (crux at morpheus.net)
Date: Mon, 28 Mar 2005 10:52:56 -0600
Subject: [clc-devel] [CLC Ticket Notification] wrong librsvg dependencies
Message-ID: <20050328165258.B343A1AB587@dream.morpheus.net>

Assigned to [clc-devel at lists.berlios.de]

The following CLC ticket (67) has been created or modified:

Description:



Remarks:



Contact: apawlik at v-lo dot krakow dot pl
CLC User: anonymous
Status: new

URL:
	http://clc.morpheus.net:6999/clc/tktview?tn=67



From crux at morpheus.net  Mon Mar 28 18:23:55 2005
From: crux at morpheus.net (crux at morpheus.net)
Date: Mon, 28 Mar 2005 12:23:55 -0600
Subject: [clc-devel] [CLC Ticket Notification] file-roller depends on nautilus
Message-ID: <20050328182358.3300B1A9FDE@dream.morpheus.net>

Assigned to [clc-devel at lists.berlios.de]

The following CLC ticket (68) has been created or modified:

Description:

file-roller does not build without nautilus installed

Remarks:



Contact: apawlik at v-lo dot krakow dot pl
CLC User: anonymous
Status: new

URL:
	http://clc.morpheus.net:6999/clc/tktview?tn=68



From jw at tks6.net  Mon Mar 28 21:50:03 2005
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 28 Mar 2005 23:50:03 +0200
Subject: [clc-devel] testing the new contrib
Message-ID: <20050328215003.GB15754@narvik.tks6.lan>

Hi,

Simone and I have set up a prtsync service on clc.morpheus.net, which
uses Jay Dolan's prtsync script to merge an arbitrary number of httpup
repositories to a single collection.

The service is set up according to the rules defined in
  http://clc.morpheus.net:6999/clc/wiki?p=NewContribRules

In case of problems and added/removed ports, notifications are sent to
clc-contrib at lists.berlios.de. An archive for this list can be seen at
  https://lists.berlios.de/pipermail/clc-contrib/

The collection itself can be found at
  http://clc.morpheus.net/prtsync/
  (http://clc.morpheus.net/prtsync/REPO)

The plan is to do an internal test this week, and do a second, public
round of testing next week.

That said, we'd like to ask for the following:
- testers who want to have their repo synced, and want to help to iron
  out bugs in the notification and merge processes
- testers who don't care about the bugs but just want to help optimizing
  the work procedure
- reviewers of the Wiki page (NewContribRules)

If you're interested in one of the above, please reply to this message.
Please also include collection name (e.g. sip, jw, etc), your email
address and the repository url. Also note that for a port to be synced,
it has to be marked explicitely with a ".sync" file (in the same
directory as the Pkgfile). Its content is ignored, so you can simply
touch it.

Known issues:
- conflict notifications are sent out hourly; this should be reduced to
  an immediate initial warning, and daily reminders
- reports about added/removed ports are send hourly; maybe those
  shouldn't go to the list, since they might not be interesting enough

Thanks for your interest.
Kind regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From crux at morpheus.net  Tue Mar 29 17:45:39 2005
From: crux at morpheus.net (crux at morpheus.net)
Date: Tue, 29 Mar 2005 11:45:39 -0600
Subject: [clc-devel] [CLC Ticket Notification] neverball fails to install.
Message-ID: <20050329174542.9857C1ABBD9@dream.morpheus.net>

Assigned to [clc-devel at lists.berlios.de]

The following CLC ticket (69) has been created or modified:

Description:



Remarks:



Contact: prologic at shortcircuit dot net dot au
CLC User: anonymous
Status: new

URL:
	http://clc.morpheus.net:6999/clc/tktview?tn=69



From jasonthomasdolan at yahoo.com  Tue Mar 29 18:12:48 2005
From: jasonthomasdolan at yahoo.com (Jay Dolan)
Date: Tue, 29 Mar 2005 10:12:48 -0800 (PST)
Subject: [clc-devel] testing the new contrib
In-Reply-To: 6667
Message-ID: <20050329181249.57997.qmail@web41503.mail.yahoo.com>

--- Johannes Winkelmann <jw at tks6.net> wrote:
> Hi,
> 
> Simone and I have set up a prtsync service on
> clc.morpheus.net, which
> uses Jay Dolan's prtsync script to merge an
> arbitrary number of httpup
> repositories to a single collection.
> 
> The service is set up according to the rules defined
> in
>  
>
http://clc.morpheus.net:6999/clc/wiki?p=NewContribRules
> 
> In case of problems and added/removed ports,
> notifications are sent to
> clc-contrib at lists.berlios.de. An archive for this
> list can be seen at
>   https://lists.berlios.de/pipermail/clc-contrib/
> 
> The collection itself can be found at
>   http://clc.morpheus.net/prtsync/
>   (http://clc.morpheus.net/prtsync/REPO)
> 
> The plan is to do an internal test this week, and do
> a second, public
> round of testing next week.
> 
> That said, we'd like to ask for the following:
> - testers who want to have their repo synced, and
> want to help to iron
>   out bugs in the notification and merge processes
> - testers who don't care about the bugs but just
> want to help optimizing
>   the work procedure
> - reviewers of the Wiki page (NewContribRules)
> 
> If you're interested in one of the above, please
> reply to this message.
> Please also include collection name (e.g. sip, jw,
> etc), your email
> address and the repository url. Also note that for a
> port to be synced,
> it has to be marked explicitely with a ".sync" file
> (in the same
> directory as the Pkgfile). Its content is ignored,
> so you can simply
> touch it.
> 
> Known issues:
> - conflict notifications are sent out hourly; this
> should be reduced to
>   an immediate initial warning, and daily reminders
> - reports about added/removed ports are send hourly;
> maybe those
>   shouldn't go to the list, since they might not be
> interesting enough
> 
> Thanks for your interest.
> Kind regards, Johannes
> -- 
> Johannes Winkelmann              mailto:jw at tks6.net
> Bern, Switzerland                http://jw.tks6.net
> _______________________________________________
> clc-devel mailing list
> clc-devel at lists.berlios.de
> http://lists.berlios.de/mailman/listinfo/clc-devel
> 

Hehe, well, I'd just like to point out that since jw
adopted prtsync for a while, it's hardly "my" script
anymore.  But I'll soon be maintaining it officially
again, and it will be available in CONTRIB (or OPT?
;)) soon - as my plan is to provide some tools for
httpup repository maintainers within the script.  I'll
also try to address the current known issues.

Jay Dolan
Software Engineer, Systems Analyst
Windmill Cycles, Inc.
508.999.4000


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 


From sip at varlock.com  Thu Mar 31 17:47:39 2005
From: sip at varlock.com (Simone Rota)
Date: Thu, 31 Mar 2005 19:47:39 +0200
Subject: [clc-devel] New CRUX/CLC website
Message-ID: <424C37BB.3050202@varlock.com>

Hi all,

some time ago I offered to help with the crux/clc website merge,
I drop you some proposal/idea in case we're going to start to work on
the project during the following weeks.

I've been evaluating some wiki package during the last days
and my preference goes to wikka wiki:

http://wikka.jsnx.com/TestSkin

for the following reasons:

- lightweight but with interesting features
- easy to configure/install/manage
- graphically customizable (ie: select the "withew.css" skin
  in the url above)
- good support for ACLs, very useful for subprojects
- does not require 3rd party software (just plain php+mysql)

In my opinion with something like Wikka we could manage the entire
CRUX/CLC website in a collaborative manner, and use cvstrac only as a
bug tracker.

======

Apart from the choice of software, we cannot really start something
without some knowledge about the physical location of the site.

Personally I'd be glad to donate some buck myself, buy some webspace
and make it accessible to CLC members.
We could host there the site, maybe with the following layout:

- isos at fukt.bth.se
- cvs and ports at morpheus.net
- webpages / docs / subprojects at the new site

This is a proposal to avoid spending time administering
(and securing) a web/db server ourselves, please let me
know if there is some interest.

As usual comments and further proposals are welcome.

Regards,
Simone


-- 
Simone Rota           WEB : http://www.varlock.com
Bergamo, Italy        MAIL: sip at varlock.com