From sip at varlock.com  Fri Nov 28 21:07:43 2003
From: sip at varlock.com (Simone Rota)
Date: Fri, 28 Nov 2003 22:07:43 +0100
Subject: [clc-devel] Future of unmaintained
In-Reply-To: <20031028214551.GB16671@hoc.LDS>
References: <20031028214551.GB16671@hoc.LDS>
Message-ID: <20031128220743.7d1b025e.sip@varlock.com>

On Tue, 28 Oct 2003 22:45:51 +0100
Johannes Winkelmann <jw at tks6.net> wrote:

> Hi there, [cut]

Hi,

> So the question is: should we leave unmaintained the way it is, losing
> potential updates, or should we define some basic rules on creating
> patches?

If we backup somewhere old ports for maintainers reference (as you suggest below) I think it's a good idea to save the users some hassle with outdated
ports.

> Related to this is a proposition Matt made on IRC: dropping ports which
> haven't been updated for a certain amount of time, and I believe this
> could be combined with the idea to allow changes for the CLC collection:
> If no maintainer updates a port, and no no patch from a user arrived at
> CLC for $TIME, a port is moved to a place where it can still be accessed
> somehow (for historians and port developers), but not served to the user
> anymore.

This is a good idea, a volunteer could periodically run a simple
script to change the collection* / remove ports that haven't been updated
for some time.
A possible drawback: there could be ports that didn't actually released
a new version for $TIME...
Chosing a good value for $TIME could be harder than it seems.

Regards,
Simone


* this way we should have something like contrib, unmaintained and obsolete.
  Users will only get the first two as usual, maintainers (or users seeking
  for problems) could add /obsolete to cvsup checkouts.




From sip at varlock.com  Fri Nov 28 23:24:13 2003
From: sip at varlock.com (Simone Rota)
Date: Sat, 29 Nov 2003 00:24:13 +0100
Subject: [clc-devel] Future of unmaintained
In-Reply-To: <20031028215219.GE383@symlink.ch>
References: <20031028214551.GB16671@hoc.LDS>
	<20031128220743.7d1b025e.sip@varlock.com>
	<20031028215219.GE383@symlink.ch>
Message-ID: <20031129002413.5eff144b.sip@varlock.com>

On Tue, 28 Oct 2003 22:52:19 +0100
Markus Ackermann <maol at symlink.ch> wrote:

[about obsolete ports] 
> I wouldn't distribute it via cvsup, too many users would just enable it
> because someone tells them to do it ("take it from there...").

We could all sign a NDA about the existance obsolete ports and use a
collection name such as "lsdjflsdjwerkwer6ewr0234324dasdk" :-)

> Every maintainer already has CVS access, so just removing all tags from
> a port would make it obsolete automatically.

Jokes apart, your solution is fine for me.

Regards,
Simone


From dkg at con-fuse.org  Wed Nov  5 12:38:13 2003
From: dkg at con-fuse.org (Daniel K. Gebhart)
Date: Wed, 5 Nov 2003 13:38:13 +0100
Subject: [clc-devel] Crux at Linuxday 2003 in Austria
Message-ID: <20031105123813.GA18793@sperrstunde.at>

Hi,

 I'll represent Crux at [1]Linuxday 2003 in Austria/Vorarlberg this year.
I plan to give a talk about Crux and show how easy it is to build ports.
There will also be a both only for Crux for which I'll be responsible. I
would really need some promo stuff like posters, t-shirts, stickers, pins,
etc. Does anyone of you is able to produce some? Any suggestions?

 Also any help in building slides or menpower at the both is very welcome!

so long,
 Daniel

-- 
Daniel K. Gebhart                               http://dkg.con-fuse.org/
Institute for Computer Science                   University of Innsbruck
Fon: (office): +43 512 507 6490     Mail: <daniel.gebhart(at)uibk.ac.at>


From dkg at con-fuse.org  Thu Nov  6 15:12:03 2003
From: dkg at con-fuse.org (Daniel K. Gebhart)
Date: Thu, 6 Nov 2003 16:12:03 +0100
Subject: [clc-devel] website - People
Message-ID: <20031106151203.GC6535@sperrstunde.at>

Hi,

 Who is responsible for editing the website at the moment? Could you
please fix my name to: 'Daniel K. Gebhart' and my nick to 'con-fuse'?

btw, why isn't this site sorted by name or status? Would make sense imho.

cheers and thanks, 
 Daniel

-- 
Daniel K. Gebhart                               http://dkg.con-fuse.org/
Institute for Computer Science                   University of Innsbruck
Fon: (office): +43 512 507 6490     Mail: <daniel.gebhart(at)uibk.ac.at>


From jw at tks6.net  Thu Nov  6 15:49:53 2003
From: jw at tks6.net (Johannes Winkelmann)
Date: Thu, 6 Nov 2003 16:49:53 +0100
Subject: [clc-devel] website - People
In-Reply-To: <20031106151203.GC6535@sperrstunde.at>
References: <20031106151203.GC6535@sperrstunde.at>
Message-ID: <20031106154953.GA6195@hoc>

Hi,
On Thu, Nov 06, 2003 at 16:12:03 +0100, Daniel K. Gebhart wrote:
> Hi,
> 
>  Who is responsible for editing the website at the moment?
I am.

> Could you
> please fix my name to: 'Daniel K. Gebhart' and my nick to 'con-fuse'?
I will, sorry I got your name wrong.
 
> btw, why isn't this site sorted by name or status? Would make sense imho.
It's sorted by last name (by hand, so if it's not correctly feel free to
tell me about it; I just found two errorr myself...).

Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Biel, Switzerland                http://jw.tks6.net


From rune at stokka.no  Thu Nov  6 21:20:50 2003
From: rune at stokka.no (Rune Stokka)
Date: Thu, 06 Nov 2003 22:20:50 +0100
Subject: [clc-devel] application
Message-ID: <3FAABB32.1010708@stokka.no>

Hi. I want to be a CLC maintainer. Actually Dan Mueller sent me an email 
suggesting to consider joining CLC. I have thought about it for a while 
-  and would really like to contribute to this fine community.

About me:
My name is Rune Stokka and I'm from Norway.
I've been around since Crux 0.9.3 and have enjoyed every bit. I've been 
reading the Crux mailing list and the previous port list since then. I 
haven't been as active yet - because I wanted to learn and adapt before 
contributing.
I haven't expressed my grattitudes yet for this excellent distribution 
Crux and for all the nice work done by the CLC. So for P?r and the 
people behind CLC - thank you wery much!!

As for now I have packaged a few ports available from CLC.
I would like to maintain two of my ports from unmaintained, and some 
others port I've done (if the ports concludes with others wishes of 
course). I've done some ports for Texas Calculator linking program, and 
are hoping to port tomcat (from apache project) in the nearest future.

Sincerely,
Rune Stokka



From sip at varlock.com  Tue Nov 11 15:03:47 2003
From: sip at varlock.com (Simone Rota)
Date: Tue, 11 Nov 2003 16:03:47 +0100
Subject: [clc-devel] Short pause
Message-ID: <1068563027.29806.9.camel@sip.linux>

Hi everybody,

just a quick note: I'll be busy with university projects
and exams until Nov 21; until then I won't be able
to update my ports* or contribute to CLC.

If there's the need to a quick update or fix during
these days, I'll be glad if another maintainer
could work on the update.

Thank you for your attention,
See you soon.

Simone Rota



*My current ports:
acroread    fox        nano   openoffice  txt2man
bogofilter  login.app  nedit  t1lib       xpdf






From riemer at ppprs1.phy.tu-dresden.de  Mon Nov 24 14:49:12 2003
From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer)
Date: Mon, 24 Nov 2003 15:49:12 +0100
Subject: [clc-devel] Hello and new ports...
Message-ID: <20031124144912.GA960@ppprs1.phy.tu-dresden.de>

Hello list,

I have created two ports for CRUX, jikes (fast java compiler from IBM) and
galculator (a scientific calculator based on GTK2).

You can download they here:
http://www.iapp.de/~riemer/CRUX-Ports/


Best regards, Tilo


From jw at tks6.net  Thu Nov 27 19:57:16 2003
From: jw at tks6.net (Johannes Winkelmann)
Date: Thu, 27 Nov 2003 20:57:16 +0100
Subject: [clc-devel] application
In-Reply-To: <3FAABB32.1010708@stokka.no>
References: <3FAABB32.1010708@stokka.no>
Message-ID: <20031127195716.GA8471@hoc>

Hi Rune,

On Thu, Nov 06, 2003 at 22:20:50 +0100, Rune Stokka wrote:
> Hi. I want to be a CLC maintainer. Actually Dan Mueller sent me an email 
> suggesting to consider joining CLC. I have thought about it for a while 
> -  and would really like to contribute to this fine community.

Sorry you had to wait so long; I assume most guys at CLC are busy, at
least this is true for myself.

> As for now I have packaged a few ports available from CLC.
> I would like to maintain two of my ports from unmaintained, and some 
> others port I've done (if the ports concludes with others wishes of 
> course). I've done some ports for Texas Calculator linking program, and 
> are hoping to port tomcat (from apache project) in the nearest future.
Do you have some of those port(s) online somewhere?

Best regards and please excuse the delay,
Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Biel, Switzerland                http://jw.tks6.net


From jw at tks6.net  Thu Nov 27 20:12:36 2003
From: jw at tks6.net (Johannes Winkelmann)
Date: Thu, 27 Nov 2003 21:12:36 +0100
Subject: [clc-devel] Update scenario
Message-ID: <20031127201236.GB8471@hoc>

Hey everyone,

I guess all of you have read the announcement of the upcoming CRUX 1.3
release. I was just wondering whether we could organize the update of
CLC ports a bit; I was mainly thinking about installing either a
pre-release (if there's any; Per? *g*) or 1.3 release version on some PC
and trying to build all ports which have the CONTRIB-1_2 tag. Using the
resulting list, we could very quickly set the new tags for ports which
build fine, making the number of ports to test remarkable smaller.  Even
if some ports don't build because of missing dependencies or similar,
the work required to get all ports tagged CONTRIB-1_3 would hopefully
much very shorter.
Of course, this would require an available host to test build those
packages, but that's an implementation issue not to be considered for
now :-)
Comments welcome. 

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


From sip at varlock.com  Thu Nov 27 20:27:51 2003
From: sip at varlock.com (Simone Rota)
Date: Thu, 27 Nov 2003 21:27:51 +0100
Subject: [clc-devel] Upgrade hints for 1.4
Message-ID: <1069964871.32559.20.camel@sip.linux>

Hi everybody,

since there is quite a number of new maintainers (me, for one!)
and CRUX 1.4 is coming, I think it would be interesting
to know something about the upgrade experiences of previous CRUX
releases by the "historical ones".

What were the main issues in previous releases? Was the process
s "spontaneous" or there was some formal or informal coordination
between the maintainers?

If I remember well it took some time to upgrade the clc port tree
during the 1.1 > 1.2 transtion, was it only a matter of overloaded
maintainers or there where technical issues?

Just curious. 

Best regards,
Simone



From sip at varlock.com  Thu Nov 27 21:12:01 2003
From: sip at varlock.com (Simone Rota)
Date: Thu, 27 Nov 2003 22:12:01 +0100
Subject: [clc-devel] Upgrade hints for 1.4
In-Reply-To: <1069964871.32559.20.camel@sip.linux>
References: <1069964871.32559.20.camel@sip.linux>
Message-ID: <1069967521.32627.37.camel@sip.linux>

On Thu, 2003-11-27 at 21:27, Simone Rota wrote:
> Hi everybody,
> 
> since there is quite a number of new maintainers (me, for one!)
> and CRUX 1.4 is coming, [cut]

Of cour I meant 1.3...and the subject's wrong too...
I need some sleep!

bye. Simone



From sip at varlock.com  Thu Nov 27 21:15:36 2003
From: sip at varlock.com (Simone Rota)
Date: Thu, 27 Nov 2003 22:15:36 +0100
Subject: [clc-devel] Update scenario
In-Reply-To: <20031127201236.GB8471@hoc>
References: <20031127201236.GB8471@hoc>
Message-ID: <1069967736.32627.39.camel@sip.linux>

On Thu, 2003-11-27 at 21:12, Johannes Winkelmann wrote:
> Hey everyone,
> 
> I guess all of you have read the announcement of the upcoming CRUX 1.3
> release. I was just wondering whether we could organize the update of
> CLC ports a bit; I was mainly thinking about installing either a
> pre-release (if there's any; Per? *g*) or 1.3 release version on some PC
> and trying to build all ports which have the CONTRIB-1_2 tag. Using the
> resulting list, we could very quickly set the new tags for ports which
> build fine, making the number of ports to test remarkable smaller.  Even
> if some ports don't build because of missing dependencies or similar,
> the work required to get all ports tagged CONTRIB-1_3 would hopefully
> much very shorter.
> Of course, this would require an available host to test build those
> packages, but that's an implementation issue not to be considered for
> now :-)
> Comments welcome. 

Hi Johannes,
(sorry, I also replied to your private address)

As I wrote some time ago I'm dedicating a machine
to the automatic clc port building process. I'm currently
tuning up the build and report script(s). My intention was to
begin with the project from CRUX 1.3 onwards-

Since the machine in question is available at the moment, I volunteer
for the test builds (with a pre-release or as soon as 1.3 goes gold).

One problem (which I'm also experiencing with the automated building
process): opt ports don't have dependencies, causing
prt-get depinst fail with ports requiring some port from /opt.
Should we assume all opt ports are installed for this test?

Bye

Simone




From giulivonavigante at tiscali.it  Fri Nov 28 01:54:11 2003
From: giulivonavigante at tiscali.it (Giulivo Navigante)
Date: Fri, 28 Nov 2003 02:54:11 +0100
Subject: [clc-devel] at port
Message-ID: <20031128025411.633e8bc9.giulivonavigante@tiscali.it>

hi all,
i have a port for "at" a batch schduler and job spooler

the Pkgfile respect yours guidelines, how can i publish this port?

thank you
byez!
-- 
Giulivo Navigante [CRUX Linux]
Freedom is The Reason, GNU/Linux is The Way


From rrm3 at rrm3.org  Fri Nov 28 05:16:13 2003
From: rrm3 at rrm3.org (Robert McMeekin)
Date: Fri, 28 Nov 2003 00:16:13 -0500
Subject: [clc-devel] Upgrade hints for 1.4
In-Reply-To: <1069964871.32559.20.camel@sip.linux>
References: <1069964871.32559.20.camel@sip.linux>
Message-ID: <20031128051613.GA23546@station.localdomain>

Simone Rota wrote:
[...]
> If I remember well it took some time to upgrade the clc port
> tree during the 1.1 > 1.2 transtion, was it only a matter of
> overloaded maintainers or there where technical issues?

I know I'm not a "historical one," but it took me a long time
because my computer is slow; which is probably why I rushed to
check-in all the changes once everything was built.  Last time,
Matt had already built a lot of the GNOME ports before I'd even
gotten started, so he tagged them--and I felt relieved (thanks 
again Matt).

Anyway, I like the thought of having a machine dedicated to
building the ports and notifying us when something doesn't work
right.  With something like that setup, we would probably only
need a few days to get everything fairly well in line--with the
right timing and a pre-release, we might even be able to get the
ports tagged in sync with the release.  (Not that I've ever had 
a problem, really, with the way things are now).

BTW, it was Thanksgiving here in the States and I ate /really/ 
well and I thought I'd share that with everybody  :-P

-- 
Robert McMeekin <rrm3 at rrm3.org>
http://www.rrm3.org/


From jw at tks6.net  Fri Nov 28 06:55:39 2003
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 28 Nov 2003 07:55:39 +0100
Subject: [clc-devel] at port
In-Reply-To: <20031128025411.633e8bc9.giulivonavigante@tiscali.it>
References: <20031128025411.633e8bc9.giulivonavigante@tiscali.it>
Message-ID: <20031128065539.GA541@hoc>

Hi Giulivo,

On Fri, Nov 28, 2003 at 02:54:11 +0100, Giulivo Navigante wrote:
> hi all,
> i have a port for "at" a batch schduler and job spooler
> 
> the Pkgfile respect yours guidelines, how can i publish this port?
Sure feel free :-)

If you want to become a CLC maintainer please read the maintainer
guidelines and write an application (examples can be found in the
archives of this mailing list). If you have question regarding this feel
free to ask.

Best regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Biel, Switzerland                http://jw.tks6.net


From jw at tks6.net  Fri Nov 28 07:00:28 2003
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 28 Nov 2003 08:00:28 +0100
Subject: [clc-devel] Update scenario
In-Reply-To: <1069967736.32627.39.camel@sip.linux>
References: <20031127201236.GB8471@hoc> <1069967736.32627.39.camel@sip.linux>
Message-ID: <20031128070028.GB541@hoc>

Hi Simone,

On Thu, Nov 27, 2003 at 22:15:36 +0100, Simone Rota wrote:
> On Thu, 2003-11-27 at 21:12, Johannes Winkelmann wrote:
> > Hey everyone,
> > 
[...]
> 
> Hi Johannes,
> (sorry, I also replied to your private address)
> 
> As I wrote some time ago I'm dedicating a machine
> to the automatic clc port building process. I'm currently
> tuning up the build and report script(s). My intention was to
> begin with the project from CRUX 1.3 onwards-
> 
> Since the machine in question is available at the moment, I volunteer
> for the test builds (with a pre-release or as soon as 1.3 goes gold).
Cool! I remembered your machine but didn't want to put any pressure on
you :-)
 
> One problem (which I'm also experiencing with the automated building
> process): opt ports don't have dependencies, causing
> prt-get depinst fail with ports requiring some port from /opt.
> Should we assume all opt ports are installed for this test?
Well, I guess as the primary task is to see whether the packages build
we should just install everything from opt; checking the deps is an
important thing as well, but really a completely different story (which
I'm not that concerned ATM ;-)).

Thanks in advance, 
Regards Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Biel, Switzerland                http://jw.tks6.net


From martin.opel at informatik.fh-regensburg.de  Fri Nov 28 07:31:05 2003
From: martin.opel at informatik.fh-regensburg.de (Martin Opel)
Date: Fri, 28 Nov 2003 08:31:05 +0100 (CET)
Subject: [clc-devel] Update scenario
In-Reply-To: <20031127201236.GB8471@hoc>
References: <20031127201236.GB8471@hoc>
Message-ID: <Pine.LNX.4.58.0311280822320.19629@rfhpc8082.fh-regensburg.de>

On Thu, 27 Nov 2003, Johannes Winkelmann wrote:

> Hey everyone,

Hi everyone,

> I guess all of you have read the announcement of the upcoming CRUX 1.3
> release. I was just wondering whether we could organize the update of
> CLC ports a bit; I was mainly thinking about installing either a
> pre-release (if there's any; Per? *g*) or 1.3 release version on some PC
> and trying to build all ports which have the CONTRIB-1_2 tag. Using the
> resulting list, we could very quickly set the new tags for ports which
> build fine, making the number of ports to test remarkable smaller.  Even
> if some ports don't build because of missing dependencies or similar,
> the work required to get all ports tagged CONTRIB-1_3 would hopefully
> much very shorter.

A prerelease would be cool. Or Per gives 1.3 first to the maintainers and
one week later to the public?

I vote for a duration of let's say two or three weeks, where every
maintainer may tag every port CONTRIB-1_3 (if no changes are necessary!).
The most annoying thing IMHO is to have to wait for another maintainer,
until he updates a port you need because of dependencies.

What's your opinion?

Bye
Martin

P.S. What about the new maintainer applications Tilo Riemer and who was
the other one?

--
martin opel / fachbereich informatik - fachhochschule regensburg
           / email: martin.opel at informatik.fh-regensburg.de
          / web: http://rfhs8012.fh-regensburg.de/~opel/
         / phone: +49 941 943-1336, fax: +49 941 943-1426


From jw at tks6.net  Fri Nov 28 08:12:18 2003
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 28 Nov 2003 09:12:18 +0100
Subject: [clc-devel] Update scenario
In-Reply-To: <Pine.LNX.4.58.0311280822320.19629@rfhpc8082.fh-regensburg.de>
References: <20031127201236.GB8471@hoc> <Pine.LNX.4.58.0311280822320.19629@rfhpc8082.fh-regensburg.de>
Message-ID: <20031128081218.GA831@hoc>

Hi,
On Fri, Nov 28, 2003 at 08:31:05 +0100, Martin Opel wrote:
> On Thu, 27 Nov 2003, Johannes Winkelmann wrote:
> 
> > Hey everyone,
> 
> Hi everyone,
[...] 
> A prerelease would be cool. Or Per gives 1.3 first to the maintainers and
> one week later to the public?
> 
> I vote for a duration of let's say two or three weeks, where every
> maintainer may tag every port CONTRIB-1_3 (if no changes are necessary!).
INHO, one week should be enough, else it gets annoying for Per as people
start using the pre release. Especially if we have a build machine,
transformation of say 80% of the ports should be done within the first
two days I assume.

Maybe we can lay down some general time plan for releases together with
Per to improve the overall experience for users of ports from CLC.

> P.S. What about the new maintainer applications Tilo Riemer and who was
Wasn't Rune Stokka the only one sending an application?

Best regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Biel, Switzerland                http://jw.tks6.net


From riemer at ppprs1.phy.tu-dresden.de  Fri Nov 28 10:24:15 2003
From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer)
Date: Fri, 28 Nov 2003 11:24:15 +0100
Subject: [clc-devel] Update scenario
In-Reply-To: <20031128081218.GA831@hoc>
References: <20031127201236.GB8471@hoc> <Pine.LNX.4.58.0311280822320.19629@rfhpc8082.fh-regensburg.de> <20031128081218.GA831@hoc>
Message-ID: <20031128102415.GB14971@ppprs1.phy.tu-dresden.de>

Hello,

> > P.S. What about the new maintainer applications Tilo Riemer and who was
> Wasn't Rune Stokka the only one sending an application?

I sent an email some days ago... I have two ports generated (jikes,
galculator). you can download they from here:

http://www.iapp.de/~riemer/


Best regards, Tilo


From per at fukt.bth.se  Fri Nov 28 11:01:29 2003
From: per at fukt.bth.se (Per Liden)
Date: Fri, 28 Nov 2003 12:01:29 +0100 (CET)
Subject: [clc-devel] Update scenario
In-Reply-To: <20031128081218.GA831@hoc>
References: <20031127201236.GB8471@hoc> <Pine.LNX.4.58.0311280822320.19629@rfhpc8082.fh-regensburg.de>
 <20031128081218.GA831@hoc>
Message-ID: <Pine.LNX.4.58.0311281146190.660@main>

Hi,

On Fri, 28 Nov 2003, Johannes Winkelmann wrote:

> On Fri, Nov 28, 2003 at 08:31:05 +0100, Martin Opel wrote:
> [...]
> > A prerelease would be cool. Or Per gives 1.3 first to the maintainers and
> > one week later to the public?

Yes, I plan to make a test ISO available before the real release is made.

> > I vote for a duration of let's say two or three weeks, where every
> > maintainer may tag every port CONTRIB-1_3 (if no changes are necessary!).
> INHO, one week should be enough, else it gets annoying for Per as people
> start using the pre release. Especially if we have a build machine,
> transformation of say 80% of the ports should be done within the first
> two days I assume.
>
> Maybe we can lay down some general time plan for releases together with
> Per to improve the overall experience for users of ports from CLC.

Sure. My problem at the moment is that I'm waiting for the 2.4.23 kernel.
Once that kernel is released I will start the bootstrapping and ISO
creation which will might take 2-4 days (depending on what other real life
things pop up).

/Per


From sip at varlock.com  Fri Nov 28 12:25:43 2003
From: sip at varlock.com (Simone Rota)
Date: Fri, 28 Nov 2003 13:25:43 +0100
Subject: [clc-devel] Update scenario
In-Reply-To: <20031128070028.GB541@hoc>
References: <20031127201236.GB8471@hoc>
	 <1069967736.32627.39.camel@sip.linux>  <20031128070028.GB541@hoc>
Message-ID: <1070022342.220.24.camel@sip.linux>

On Fri, 2003-11-28 at 08:00, Johannes Winkelmann wrote:
> Hi Simone,

> > Since the machine in question is available at the moment, I volunteer
> > for the test builds (with a pre-release or as soon as 1.3 goes gold).
> Cool! I remembered your machine but didn't want to put any pressure on
> you :-)
Regarding this topic, I often have proposals and projects around
CRUX, but never find th time to finish them. :/
I'm free from exams until the end of January, so this is a good period
for CRUXing.
 
[deps]
> Well, I guess as the primary task is to see whether the packages build
> we should just install everything from opt; checking the deps is an
> important thing as well, but really a completely different story (which
> I'm not that concerned ATM ;-)).

Ok, so as soon as Per releases a test ISO (as I see in this
thread it should happen), I'll prepare the machine
with all /base and /opt ports and launch the build process
for all clc ports.

For the moment we'd assume dependencies are correct:
I'll simply launch a prt-get depinst for each port
without removing the installed ports at the end of
each loop.

What about /unmaintained? should I test also these one?
(of course after all /contrib are checked). I suspect
there could be quite a few outdated ports over there.

Regards,
Simone




From martin.opel at informatik.fh-regensburg.de  Fri Nov 28 12:45:33 2003
From: martin.opel at informatik.fh-regensburg.de (Martin Opel)
Date: Fri, 28 Nov 2003 13:45:33 +0100 (CET)
Subject: [clc-devel] Update scenario
In-Reply-To: <1070022342.220.24.camel@sip.linux>
References: <20031127201236.GB8471@hoc>  <1069967736.32627.39.camel@sip.linux>
  <20031128070028.GB541@hoc> <1070022342.220.24.camel@sip.linux>
Message-ID: <Pine.LNX.4.58.0311281342360.19629@rfhpc8082.fh-regensburg.de>

On Fri, 28 Nov 2003, Simone Rota wrote:
...
> For the moment we'd assume dependencies are correct:
> I'll simply launch a prt-get depinst for each port
> without removing the installed ports at the end of
> each loop.

You should remove everything but base/opt after each loop to get the best
results.

> What about /unmaintained? should I test also these one?
> (of course after all /contrib are checked). I suspect
> there could be quite a few outdated ports over there.

No. UNMAINTAINED is UNMAINTAINED is UNMAINTAINED :)
There's no version number.

Bye
Martin

--
martin opel / fachbereich informatik - fachhochschule regensburg
           / email: martin.opel at informatik.fh-regensburg.de
          / web: http://rfhs8012.fh-regensburg.de/~opel/
         / phone: +49 941 943-1336, fax: +49 941 943-1426


From sip at varlock.com  Fri Nov 28 13:30:09 2003
From: sip at varlock.com (Simone Rota)
Date: Fri, 28 Nov 2003 14:30:09 +0100
Subject: [clc-devel] Update scenario
In-Reply-To: <Pine.LNX.4.58.0311281342360.19629@rfhpc8082.fh-regensburg.de>
References: <20031127201236.GB8471@hoc>
	 <1069967736.32627.39.camel@sip.linux> <20031128070028.GB541@hoc>
	 <1070022342.220.24.camel@sip.linux>
	 <Pine.LNX.4.58.0311281342360.19629@rfhpc8082.fh-regensburg.de>
Message-ID: <1070026208.215.86.camel@sip.linux>

On Fri, 2003-11-28 at 13:45, Martin Opel wrote:
> > I'll simply launch a prt-get depinst for each port
> > without removing the installed ports at the end of
> > each loop.
> 
> You should remove everything but base/opt after each loop to get the best
> results.

Ok.

> > What about /unmaintained? should I test also these one?
> No. UNMAINTAINED is UNMAINTAINED is UNMAINTAINED :)
> There's no version number.

:)
I thought it would be fine to have an idea of how many
ports from unmaintaned will build. Anyway, I'll concentrate
on /contrib for now.

Regards,
Simone



From rune at stokka.no  Fri Nov 28 19:13:44 2003
From: rune at stokka.no (rune at stokka.no)
Date: Fri, 28 Nov 2003 20:13:44 +0100
Subject: [clc-devel] application
In-Reply-To: <20031127195716.GA8471@hoc>
References: <3FAABB32.1010708@stokka.no> <20031127195716.GA8471@hoc>
Message-ID: <3FC79E68.7080709@stokka.no>

Hi,

Johannes Winkelmann wrote:

>Do you have some of those port(s) online somewhere?
>
>  
>
The ports in question are now located here:
http://www.stokkabygg.no/rune/

>Best regards and please excuse the delay,
>Johannes
>  
>
Nothing to be sorry about :) I assumed Simone was not the only one 
having exams...

Bye

Rune