From sip at varlock.com  Mon Jan  5 00:11:37 2004
From: sip at varlock.com (Simone Rota)
Date: Mon, 05 Jan 2004 01:11:37 +0100
Subject: [clc-devel] Ports reorganisation?
Message-ID: <1073261494.5857.61.camel@sip.linux>

Hi everybody,
since it's been quiet for a while, I'll do my best to annoy
you all as usual.

Some consideration about the current CLC port tree and related
topics:

[*** unmaintained ***]
Some time ago we discussed about a possible removal of the
/unmaintained collection; I suggest to open up the previous
to casual contributors and not-so-tested ports, in an effort
to unify the many spotted httpup collections.
The 'new' unmaintained collection would of course be totally
unsupported, and be separate from /contrib.
This could be done in other ways than cvs, if needed.(httpup hack?)

[*** mea culpa ***]
I'm ditching my httpup repository. I'll try to:
- transfer the useful ports into /contrib
- remove duplicate ports
- trash the one I rarely use

(Who cares, you'll say)
As a CLC maintainer I found that having a separate repository
often ends up with duplicated ports, de-centralization, etc.

Additionally It's quite common for me (as for many others I suppose) 
to create custom ports from scratch or with slight modifications
or updates of existing ports, thus adding other mess to the ports
available on my system. I'm going to stop this trend, removing
the unneeded ports and try to collaborate a little more with other
maintainers, eventually explaining why I feel my port is
an improvement. Btw, this could be easier with a more open /unmaintained
collection.

[*** opinions? ***]
I think a global step towards stricter collaboration and centralization
of ports* could improve the CRUX user experience and save precious
manpower (packagerpower?). In my opinion this point is particularly
important, since the CRUX community cannot count on thoushands
of contributors. What do you think?

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


* Of course private httpup repos of most exotic / highly customized
stuff will continue to exist.



From danm at gmx.li  Mon Jan  5 21:37:01 2004
From: danm at gmx.li (Daniel Mueller)
Date: Mon, 5 Jan 2004 22:37:01 +0100
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <1073261494.5857.61.camel@sip.linux>
References: <1073261494.5857.61.camel@sip.linux>
Message-ID: <20040105223701.5c9fc313@torax.danm.de>

Hi Simone,

On Mon, 05 Jan 2004 01:11:37 +0100
Simone Rota <sip at varlock.com> wrote:

> [*** unmaintained ***]
> Some time ago we discussed about a possible removal of the
> /unmaintained collection; I suggest to open up the previous
> to casual contributors and not-so-tested ports, in an effort
> to unify the many spotted httpup collections.

I personally vote for removing 'unmaintained' completely. I'm a big fan
of httpup repositories, because they're giving a wide range of people
the chance to distribute their ports. Not every user has (shell-)
access to a server for running cvsupd. Webspace is cheap & everywhere
available.

> (Who cares, you'll say)
> As a CLC maintainer I found that having a separate repository
> often ends up with duplicated ports, de-centralization, etc.

De-centralization would be okay - but we need a central index of all
ports.

-- 
Daniel Mueller
Berlin, Germany		(OpenPGP:  1024D/126EC290)


From sip at varlock.com  Mon Jan  5 23:33:56 2004
From: sip at varlock.com (Simone Rota)
Date: Tue, 06 Jan 2004 00:33:56 +0100
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <20040105223701.5c9fc313@torax.danm.de>
References: <1073261494.5857.61.camel@sip.linux>
	 <20040105223701.5c9fc313@torax.danm.de>
Message-ID: <1073345635.19185.20.camel@sip.linux>

On Mon, 2004-01-05 at 22:37, Daniel Mueller wrote:
> Hi Simone,
Hi Daniel,

> I personally vote for removing 'unmaintained' completely. I'm a big fan
> of httpup repositories, because they're giving a wide range of people
> the chance to distribute their ports. Not every user has (shell-)
> access to a server for running cvsupd. Webspace is cheap & everywhere
> available.

> De-centralization would be okay - but we need a central index of all
> ports.

I guess for some aspect is a matter of personal taste.
The idea of a central index of httpup repos is good, in fact
I've been using a port containing httpup files for a while
(actually some consideration in my previous mail
comes from experiences using that port).

My point is that a central repository of 3rd party
(or unmaintained if you prefer) would:
- limit duplicates
- improve the quality of ports: in theory ports from the
  common repository are more exposed to the users, thus
  possible problems are easier to discover.

I won't mind if the various httpup repos are physically
on a central server or not (CLC providing
a central index as you suggest), so I think we
share some point.

Of course we should consider security implications,
but that's another story.

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




From jw at tks6.net  Fri Jan  9 09:40:42 2004
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 9 Jan 2004 10:40:42 +0100
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <1073261494.5857.61.camel@sip.linux>
References: <1073261494.5857.61.camel@sip.linux>
Message-ID: <20040109094042.GA459@hoc>

Hello,

First of all best wishes for 2004. It's probably a good time to think
and discuss a bit about CLC, but first of all I'd like to thank everyone
involved in CLC including the new maintainers:
The web database (which is always a few ports off though ;-)) says we
have 464 ports in contrib, 310 in unmaintained. Now I personally think
this is great compared to the situation we had earlier.

On Mon, Jan 05, 2004 at 01:11:37 +0100, Simone Rota wrote:
> Hi everybody,
> since it's been quiet for a while, I'll do my best to annoy
> you all as usual.
> 
> Some consideration about the current CLC port tree and related
> topics:
> 
> [*** unmaintained ***]
> Some time ago we discussed about a possible removal of the
> /unmaintained collection; I suggest to open up the previous
> to casual contributors and not-so-tested ports, in an effort
> to unify the many spotted httpup collections.
> The 'new' unmaintained collection would of course be totally
> unsupported, and be separate from /contrib.
I've discussed with J?rgen and Martin regarding unmaintained, and I now
think that we should keep it and define a procedure to allow submission
of changes back to it. This is because of the higher level of trust
because someone from CLC at least _looked_ at it ("many eyes" as Martin
called this). IMHO this is a very good argument.
The important thing here is to make sure that applying submitted changes
is really simple and that a lot of checks are done by scripts (e.g.
footprints).
And finally I'd keep the policy that ports from unmaintained should
automatically lose their UNMAINTAINED tag when not touched for
$SOME_TIME. Like this, only actively used ports remain in our collections.
Of course, there should be a warning mail to a mailing list ("port XY is
about to be removed from unmaintained").

> [*** mea culpa ***]
> I'm ditching my httpup repository. I'll try to:
> - transfer the useful ports into /contrib
> - remove duplicate ports
> - trash the one I rarely use
> 
> (Who cares, you'll say)
> As a CLC maintainer I found that having a separate repository
> often ends up with duplicated ports, de-centralization, etc.
> 
> Additionally It's quite common for me (as for many others I suppose) 
> to create custom ports from scratch or with slight modifications
> or updates of existing ports, thus adding other mess to the ports
> available on my system. I'm going to stop this trend, removing
> the unneeded ports and try to collaborate a little more with other
> maintainers, eventually explaining why I feel my port is
> an improvement. Btw, this could be easier with a more open /unmaintained
> collection.
I agree with most parts of what you say. When looking at the current
httpup repositories, I think the amount of duplication is not that bad
though. IMO there is room for both CLC and private httpup repositories,
just because I think there are ports which are too specific or
functional duplicates (which doesn't make them exotic yet).

I just think we should first of all open unmaintained for contributions
so people don't duplicate newer versions of these ports in their httpup
repos. Then we should try to propagate httpup repositories with a
certain standard (e.g. no dups). I could even imagine to have to kind of
"clc-contrib" subproject, which fetches the httpup repositories from the
respective httpup maintainers and serves it as a single httpup repo.
This would also be the place to recruit new maintainers.

Of course, this is probably quite some work, and we lose the "many eyes"
advantage.

> [*** opinions? ***]
> I think a global step towards stricter collaboration and centralization
> of ports* could improve the CRUX user experience and save precious
> manpower (packagerpower?). In my opinion this point is particularly
> important, since the CRUX community cannot count on thoushands
> of contributors. What do you think?
I think it's central port availability is quite important; to me the
"many eyes" argument counts even more though.


Looking forward to some more comments,
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 Jan  9 12:29:38 2004
From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer)
Date: Fri, 9 Jan 2004 13:29:38 +0100
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <20040109094042.GA459@hoc>
References: <1073261494.5857.61.camel@sip.linux> <20040109094042.GA459@hoc>
Message-ID: <20040109122938.GE24027@ppprs1.phy.tu-dresden.de>

Hello,

> I've discussed with J?rgen and Martin regarding unmaintained, and I now
> think that we should keep it and define a procedure to allow submission
> of changes back to it. This is because of the higher level of trust
> because someone from CLC at least _looked_ at it ("many eyes" as Martin
> called this). IMHO this is a very good argument.
> The important thing here is to make sure that applying submitted changes
> is really simple and that a lot of checks are done by scripts (e.g.
> footprints).

Who should be able to submit changes? If someone can change Pkgfile he
should also be able to change footprints. And he could replace a link with a
link pointing at a backdoor...


Best regards, Tilo


From tillbiedermann at yahoo.de  Fri Jan  9 23:54:30 2004
From: tillbiedermann at yahoo.de (Till Biedermann)
Date: Sat, 10 Jan 2004 00:54:30 +0100
Subject: [clc-devel] crux-ports-database
Message-ID: <1073692470.6443.31.camel@Horst.wg.lan>

hi

i am working on a database for crux-ports.

this database shoud not be for cvs-ports, because they are easy to
browse, search and use with prt-get and the list at clc.berlios.de.

but when you need a progam that is not a cvs port, you have to search
all websites where ports are avalible or install all httup repositorys.
and httups are not so easy to handle with prt-get.

that is no good solution imho.

i know that there are several solutions in discusion and that a 'real'
linux-tool would be the best way.
but i think it would be nice to have a database where every ever created
port for crux is listed. this is especially  for new crux users a good
thing. so they can see if the software they need is avalible.

so here is my suggestion:

http://www.polarhome.com:793/~till

it is at the moment only filled with dummies for testing.
everybody who makes ports for the software he uses could enter his port
in the database.
updating and deleting entries is also possible.

now only a search function is nessesary (the front end is already
there).

so please tell me your opinion.


regards till





From jw at tks6.net  Sat Jan 10 12:33:54 2004
From: jw at tks6.net (Johannes Winkelmann)
Date: Sat, 10 Jan 2004 13:33:54 +0100
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <20040109122938.GE24027@ppprs1.phy.tu-dresden.de>
References: <1073261494.5857.61.camel@sip.linux> <20040109094042.GA459@hoc> <20040109122938.GE24027@ppprs1.phy.tu-dresden.de>
Message-ID: <20040110123354.GA691@hoc>

Hi,

On Fri, Jan 09, 2004 at 13:29:38 +0100, Tilo Riemer wrote:
> Hello,
> 
> > I've discussed with J?rgen and Martin regarding unmaintained, and I now
> > think that we should keep it and define a procedure to allow submission
> > of changes back to it. This is because of the higher level of trust
> > because someone from CLC at least _looked_ at it ("many eyes" as Martin
> > called this). IMHO this is a very good argument.
> > The important thing here is to make sure that applying submitted changes
> > is really simple and that a lot of checks are done by scripts (e.g.
> > footprints).
> 
> Who should be able to submit changes? If someone can change Pkgfile he
> should also be able to change footprints. And he could replace a link with a
> link pointing at a backdoor...
Yeah, that's very true. It's still a lot better if it's reviewed, right?
I consider it an improvement if someone independent had a look at it
compared to just using the same port from someone's httpup repo. It's
just a higher level of trust, not a perfect secure solution.

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


From jw at tks6.net  Sat Jan 10 12:49:11 2004
From: jw at tks6.net (Johannes Winkelmann)
Date: Sat, 10 Jan 2004 13:49:11 +0100
Subject: [clc-devel] crux-ports-database
In-Reply-To: <1073692470.6443.31.camel@Horst.wg.lan>
References: <1073692470.6443.31.camel@Horst.wg.lan>
Message-ID: <20040110124911.GB691@hoc>

Hi Till,

On Sat, Jan 10, 2004 at 00:54:30 +0100, Till Biedermann wrote:
> hi
> 
> i am working on a database for crux-ports.
Great

> this database shoud not be for cvs-ports, because they are easy to
> browse, search and use with prt-get and the list at clc.berlios.de.
Mmmh, I think there should be only one search page for everything,
including CVSup ports. Unfortunately our disk quota at Berlios is not
large enough to host such a database there. If we can find a solution
for that, I'd gladly contribute the current implemention of the search
DB.
Especially for new users it's very confusing to have many search
databases...

[...]
> i know that there are several solutions in discusion and that a 'real'
> linux-tool would be the best way.
Well, a web based solution is nice because you can access it from any
platform.

> so here is my suggestion:
> 
> http://www.polarhome.com:793/~till
> 
> it is at the moment only filled with dummies for testing.
> everybody who makes ports for the software he uses could enter his port
> in the database.
I'd rather go for a database which is generated from the ports, not
updated by users. If you look at it from a packagers view, it's
duplicate work if you have to update the web entry for every change you
do in a Pkgfile. There seems to be such an index of httpup repos
already:
  http://www.mikropiiri.org/crux/httpup_index.html

Well, I'm looking forward to some other comments though :-)
Best regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Biel, Switzerland                http://jw.tks6.net


From tillbiedermann at yahoo.de  Sat Jan 10 14:06:14 2004
From: tillbiedermann at yahoo.de (Till Biedermann)
Date: Sat, 10 Jan 2004 15:06:14 +0100
Subject: [clc-devel] crux-ports-database
In-Reply-To: <20040110124911.GB691@hoc>
References: <1073692470.6443.31.camel@Horst.wg.lan>
	 <20040110124911.GB691@hoc>
Message-ID: <1073743574.21663.32.camel@Horst.wg.lan>

hi johannes

On Sat, 2004-01-10 at 13:49, Johannes Winkelmann wrote:
> Mmmh, I think there should be only one search page for everything,
> including CVSup ports..............Especially for new users it's very
> confusing to have many search databases...
> 

i agree. it should be no problem to integrate cvs ports in the database.

> I'd rather go for a database which is generated from the ports, not
> updated by users. If you look at it from a packagers view, it's
> duplicate work if you have to update the web entry for every change you
> do in a Pkgfile.

i also totally agree. but this is only an implematation of my first
ideas.

it should be also no problem to syncronice the database with cvs and
httup repositorys.

but this will require some rules. for example who updates the database
and how is the database updated: with a php-frontend, with
sql-dump-files, automatic,...

also there should be a clear concept of the database structure. i dont
know much about database-theory, so my draft is surely far away from
being perfect.

> There seems to be such an index of httpup repos
> already:
>   http://www.mikropiiri.org/crux/httpup_index.html
> 

nice. i did not know that page. but this one seems to be generated from
installed httpup-port-directories. so the completeness is not
guaranteed. also this page it is well hidden. so this is no help for new
crux-users.

regards till




From tillbiedermann at yahoo.de  Sun Jan 11 00:16:56 2004
From: tillbiedermann at yahoo.de (Till Biedermann)
Date: Sun, 11 Jan 2004 01:16:56 +0100
Subject: [clc-devel] crux-ports-database
In-Reply-To: <20040110124911.GB691@hoc>
References: <1073692470.6443.31.camel@Horst.wg.lan>
	 <20040110124911.GB691@hoc>
Message-ID: <1073780216.6142.5.camel@Horst.wg.lan>

hi

On Sat, 2004-01-10 at 13:49, Johannes Winkelmann wrote:
> I'd rather go for a database which is generated from the ports, not
> updated by users. 

well, here it is:

http://www.polarhome.com:793/~till/crux_database2


only the httup-file is needed. the script searches the database for
existing entries updates them and add the new ones.

regards till





From tillbiedermann at yahoo.de  Sun Jan 11 17:24:51 2004
From: tillbiedermann at yahoo.de (Till Biedermann)
Date: Sun, 11 Jan 2004 18:24:51 +0100
Subject: [clc-devel] crux-ports-database
In-Reply-To: <20040110124911.GB691@hoc>
References: <1073692470.6443.31.camel@Horst.wg.lan>
	 <20040110124911.GB691@hoc>
Message-ID: <1073841891.1893.21.camel@Horst.wg.lan>

hi

now the first fully usable version is ready.

http://www.polarhome.com:793/~till/


containing all (nearly all) avalible ports. the database is searchable
by port-names and repositories. the database is simply updated by
submitting the URL to the httpup file of the repository.


known problems:

-the server currently hosting the database is often very slow.
-if the description of the port in the Pkgfile contains signs that php
interprets as string-end an sql-syntax error appears and this port is
not added to the database.
-a serious problem, that i cant understand is that the
unmaintained-repository cant be updated.
because there are no problems with the other cvs-repositories i guess
that this problem is not caused by my script.


regards till 




From dkg at con-fuse.org  Mon Jan 12 19:49:36 2004
From: dkg at con-fuse.org (Daniel K. Gebhart)
Date: Mon, 12 Jan 2004 20:49:36 +0100
Subject: [clc-devel] I'll be back soon..
Message-ID: <20040112194936.GP22129@sperrstunde.at>

Hi guys!

 I'm very sorry to have been as inactive as I have been during the last
weeks. But I've some good news. Next week I'll get my new PC and will be
able to contribute to CRUX again.

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


From rrm3 at rrm3.org  Mon Jan 12 21:20:04 2004
From: rrm3 at rrm3.org (Rob)
Date: Mon, 12 Jan 2004 16:20:04 -0500 (EST)
Subject: [clc-devel] I'll be back soon..
In-Reply-To: <20040112194936.GP22129@sperrstunde.at>
References: <20040112194936.GP22129@sperrstunde.at>
Message-ID: <200401122120.i0CLK41O019367@reveal.local>

On Mon, 12 Jan 2004 at 20:49:36 +0100, Daniel Gebhart wrote: 
>  I'm very sorry to have been as inactive as I have been during the
> last weeks. But I've some good news. Next week I'll get my new PC and
> will be able to contribute to CRUX again.

Hey, I want a new computer too! :-P, but that's not going to happen any 
time soon I don't think.  Anyway, I've been pretty inactive too, since I 
was busy taking care of a friend of mine the past weeks.  It's good to 
have you back ;-)

// Rob
-- 
  "He's a suicidal arachnophobic vampire hunter living undercover at
   Ringling Bros. Circus.  She's a cold-hearted belly-dancing doctor
   trying to make a difference in a man's world. They fight crime!"
 


From emil at unf.se  Tue Jan 13 15:21:04 2004
From: emil at unf.se (=?Windows-1252?Q?Emil_=D6sterlund?=)
Date: Tue, 13 Jan 2004 16:21:04 +0100
Subject: [clc-devel] httpresp
Message-ID: <B1437E4634B06548BED8DA64666CA0FC6E39D6@sesob03.sobernet.net>

u might wanna add this to your ports...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tam.httpup
Type: application/octet-stream
Size: 126 bytes
Desc: tam.httpup
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20040113/ffead6b6/attachment.obj>

From sip at varlock.com  Tue Jan 13 16:53:58 2004
From: sip at varlock.com (Simone Rota)
Date: Tue, 13 Jan 2004 17:53:58 +0100
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <20040109094042.GA459@hoc>
References: <1073261494.5857.61.camel@sip.linux>  <20040109094042.GA459@hoc>
Message-ID: <1074012837.18287.51.camel@sip.linux>

On Fri, 2004-01-09 at 10:40, Johannes Winkelmann wrote:
> Hello,
Hi,

> I've discussed with J?rgen and Martin regarding unmaintained, and I now
> think that we should keep it and define a procedure to allow submission
> of changes back to it. This is because of the higher level of trust
> because someone from CLC at least _looked_ at it ("many eyes" as Martin
> called this). IMHO this is a very good argument.
> The important thing here is to make sure that applying submitted changes
> is really simple and that a lot of checks are done by scripts (e.g.
> footprints).

> I just think we should first of all open unmaintained for contributions
> so people don't duplicate newer versions of these ports in their httpup
> repos. Then we should try to propagate httpup repositories with a
> certain standard (e.g. no dups). I could even imagine to have to kind of
> "clc-contrib" subproject, which fetches the httpup repositories from the
> respective httpup maintainers and serves it as a single httpup repo.
> This would also be the place to recruit new maintainers.
> 
> Of course, this is probably quite some work, and we lose the "many eyes"
> advantage.


Sorry for replying a little late, I was reading some comment about
arch linux yesterday (don't remember where, sorry. Maybe osnews.com).
I think they've a public Incoming collection or something similar;
maintainers periodically check ports submissions
and updates in this incoming collection and eventually transfer
them to unmaintained.
To me it sounds a nice system. The first maintainer that has some
spare time could do a quick check on the incoming collection
and transfer good ports.

A question arise: what to check? Since after all that ports will be
transferred to unmaintained (or 3rdparty or some other name), I suggest
maintainers should only check for a couple of security aspects:
- sources are retrieved from a proper url.
- no malicious stuff in Pkgfile "build" function.
IMHO If the port doesn't build or there are footprint issues
we should leave the users / casual contributors the task
to submit a patch to the packager or directly to the
incoming dir.

> And finally I'd keep the policy that ports from unmaintained should
> automatically lose their UNMAINTAINED tag when not touched for
> $SOME_TIME. Like this, only actively used ports remain in our collections.
> Of course, there should be a warning mail to a mailing list ("port XY is
> about to be removed from unmaintained").

Good idea, the only suggestion I have is to send
a cumulative mail  periodically (every x months)
instead of each time a port is "expiring":
Warning: the following ports will be removed: a,b,c...

> Looking forward to some more comments,
> Best regards Johannes

I hope we can find some good implementation of
the ideas coming up from this ML; I also hope
to have some more time in a month or so* to give
some help if needed.

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


* My next exams dates:
26.01 - 28.01 - 30.01 - 02.02 - 04.02 - 05.02
more to come on Feb 07..21. sic.



From martin.opel at informatik.fh-regensburg.de  Wed Jan 14 08:08:52 2004
From: martin.opel at informatik.fh-regensburg.de (Martin Opel)
Date: Wed, 14 Jan 2004 09:08:52 +0100 (CET)
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <1074012837.18287.51.camel@sip.linux>
References: <1073261494.5857.61.camel@sip.linux>  <20040109094042.GA459@hoc>
 <1074012837.18287.51.camel@sip.linux>
Message-ID: <Pine.LNX.4.58.0401140842500.1122@rfhpc8082.fh-regensburg.de>

I'm sorry for the late reply, too. I have the following suggestions:

1. unmaintained: we remove it from cvs and copy the plain files to a
http-repository. from then on it is distributed by httpup. Without the
pros and cons of cvs.

2. We write a php upload page on crux.fh-regensburg.de, where users can
upload new ports (as gzipped tarfiles). The files run through a few sanity
checks and go directly to the direcory from point 1. The web gui should
have the following features: upload a port with information about the
date, all other information can be read out of the Pkgfile headers; remove port.
So *everybody* can upload a port to the server and
*everybody* can remove every port. Could this work (wiki concept)?

3. If a maintainer wants a port of this "everybody can do
everything"-repository in contrib, the he can remove it and put it into
contrib.

I could write a part of the php code, but I have not much time the next
weeks.

Comments?

Bye
Martin


From jw at tks6.net  Wed Jan 14 09:07:54 2004
From: jw at tks6.net (Johannes Winkelmann)
Date: Wed, 14 Jan 2004 10:07:54 +0100
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <Pine.LNX.4.58.0401140842500.1122@rfhpc8082.fh-regensburg.de>
References: <1073261494.5857.61.camel@sip.linux> <20040109094042.GA459@hoc> <1074012837.18287.51.camel@sip.linux> <Pine.LNX.4.58.0401140842500.1122@rfhpc8082.fh-regensburg.de>
Message-ID: <20040114090753.GA544@hoc>

Hi Martin,

On Wed, Jan 14, 2004 at 09:08:52 +0100, Martin Opel wrote:
> 
> I'm sorry for the late reply, too. I have the following suggestions:
> 
> 1. unmaintained: we remove it from cvs and copy the plain files to a
> http-repository. from then on it is distributed by httpup. Without the
> pros and cons of cvs.
Yeah, that's fine with me

> 2. We write a php upload page on crux.fh-regensburg.de, where users can
> upload new ports (as gzipped tarfiles). The files run through a few sanity
> checks and go directly to the direcory from point 1. 
How about creating this repository from other httpup repositories?
Uploading 10+ ports via web frontend is rather inconvenient IMO. Merging
the distributed httpup's automatically would make it much cooler :-)

This would usually mean: for a port from unmaintained, copy it to your
upload directory; do some updates; upload to server -> synced
automatically

I'd suggest a discussion on GnuPG signing of REPO files to have some
information about the packager (most notable: e-mail address), and
introduce an additional md5sum check: right now, files fetched from the
web are not checked against the REPO md5sum. I could introduce a
--pedantic-md5 flag to httpup.

Of course, the problem of duplicates needs some rules. IMO packagers
should discuss how to merge their ports (of they're not equal) and
discuss their differences to get a common solution. I'm not quite sure
though what to do if they fail to find a consensus:

1. Discuss and decide in CLC?
  + probably best for the integrity
  - maybe a lot of (uninteresting) work
  - one packages gets turned down, maybe for very small reasons; doesn't
    improve his opinion of CLC
2. Have multiple ports (mplayer, mplayer-gui)
  + all kind of wishes are covered
  - updates are duplicate work
  - "packaging competition"; don't think that's a good thing

In the end I think it's not a bad approach to have duplicates and
discuss them in a dedicated mailing list, as you can learn a lot from
other packagers.


Of course, the httpup approach has some problem as well; packager can
disappear, but they're httpup repos are still online. In such cases,
we'd need to stop updating from his repo to allow others to maintain his
ports... we could require all maintainer to visit an URL with id every
month to make sure they're alive.

Comments here?
Regards, Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From martin.opel at informatik.fh-regensburg.de  Wed Jan 14 09:19:38 2004
From: martin.opel at informatik.fh-regensburg.de (Martin Opel)
Date: Wed, 14 Jan 2004 10:19:38 +0100 (CET)
Subject: [clc-devel] Ports reorganisation? 
Message-ID: <Pine.LNX.4.58.0401141019090.1122@rfhpc8082.fh-regensburg.de>

On Wed, 14 Jan 2004, Johannes Winkelmann wrote:

Overall that sounds cool for me. But as I already mentioned, I have not
much time. Is crux.fh-regensburg.de the right place? If someone needs a
shell account on that machine to develop this, I have no problem with it.
Any volunteers?

- Martin


From tillbiedermann at yahoo.de  Wed Jan 14 11:48:38 2004
From: tillbiedermann at yahoo.de (Till Biedermann)
Date: Wed, 14 Jan 2004 12:48:38 +0100
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <20040114090753.GA544@hoc>
References: <1073261494.5857.61.camel@sip.linux> <20040109094042.GA459@hoc>
	 <1074012837.18287.51.camel@sip.linux>
	 <Pine.LNX.4.58.0401140842500.1122@rfhpc8082.fh-regensburg.de>
	 <20040114090753.GA544@hoc>
Message-ID: <1074080918.339.22.camel@Horst.wg.lan>

On Wed, 2004-01-14 at 10:07, Johannes Winkelmann wrote:

> Of course, the problem of duplicates needs some rules. IMO packagers
> should discuss how to merge their ports (of they're not equal) and
> discuss their differences to get a common solution. I'm not quite sure
> though what to do if they fail to find a consensus:
> .....
> In the end I think it's not a bad approach to have duplicates and
> discuss them in a dedicated mailing list, as you can learn a lot from
> other packagers.

I agree.
I dont think duplicate ports are a problem, as  long as they use
different configure-options (for example --enable_kde) or a binay- and a
source-version AND the used options should be documented in a
README-file.
So everybody can decide for his own which port he uses.

> Of course, the httpup approach has some problem as well; packager can
> disappear, but they're httpup repos are still online. In such cases,
> we'd need to stop updating from his repo to allow others to maintain his
> ports... we could require all maintainer to visit an URL with id every
> month to make sure they're alive.
> 

That's why in my opinion the best solution is to have one point, where
everything is avalible:

-the information of the port
-and the port its self (maybe as gzip file). so you dont have to
download a complete repository only for using one port.

btw: any comments or improvment suggestions for my database?

http://cruxports.tbmnet.de/

(here is a xhtml-preview:
http://www.tbmnet.de/tbmnet.php?content=crux_ports_database
not yet xhtml strict valid)


regards till






From jw at tks6.net  Fri Jan 16 20:57:49 2004
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 16 Jan 2004 21:57:49 +0100
Subject: [clc-devel] Ports reorganisation?
In-Reply-To: <Pine.LNX.4.58.0401141019090.1122@rfhpc8082.fh-regensburg.de>
References: <Pine.LNX.4.58.0401141019090.1122@rfhpc8082.fh-regensburg.de>
Message-ID: <20040116205749.GC29083@hoc>

Hi,

On Wed, Jan 14, 2004 at 10:19:38 +0100, Martin Opel wrote:
> 
> On Wed, 14 Jan 2004, Johannes Winkelmann wrote:
> 
> Overall that sounds cool for me. But as I already mentioned, I have not
> much time. Is crux.fh-regensburg.de the right place? If someone needs a
> shell account on that machine to develop this, I have no problem with it.
> Any volunteers?
I've started writing a basic sync script which should be able to sync
ports from multiple httpup directories into a single ports dir. I don't
have that much time either, but if no one else wants to work on this
I'll just continue ;-)
I hope to have a working version around next week.

Just to let you know,
Johannes
-- 
Johannes Winkelmann              mailto:jw at tks6.net
Bern, Switzerland                http://jw.tks6.net


From danm at gmx.li  Sun Jan 18 11:34:22 2004
From: danm at gmx.li (Daniel Mueller)
Date: Sun, 18 Jan 2004 12:34:22 +0100
Subject: [clc-devel] httpresp
In-Reply-To: <B1437E4634B06548BED8DA64666CA0FC6E39D6@sesob03.sobernet.net>
References: <B1437E4634B06548BED8DA64666CA0FC6E39D6@sesob03.sobernet.net>
Message-ID: <20040118123422.3a2a6283@torax.danm.de>

Hello Emil,

Can you put this file online ? Maybe something like
'http://ogg.mine.nu/~tam/tam.httpup' ?

> #
> # /etc/ports/tam.httpup: tam's ports collection
> #
> 
> ROOT_DIR=/usr/ports/tam
> URL=http://ogg.mine.nu/~tam/ports
> 
> # End of file

bye, danm

-- 
Daniel Mueller
Berlin, Germany		(OpenPGP:  1024D/126EC290)


From MAILER-DAEMON at berlios.de  Sat Jan 17 21:06:02 2004
From: MAILER-DAEMON at berlios.de (Mail Delivery Subsystem)
Date: Sat, 17 Jan 2004 22:06:02 +0100
Subject: [clc-devel] Returned mail: see transcript for details
Message-ID: <200401172106.i0HL62a28211@bat.berlios.de>

The original message was received at Sat, 17 Jan 2004 22:06:01 +0100
from rfhs0023.fh-regensburg.de [194.95.104.23]

   ----- The following addresses had permanent fatal errors -----
viper at mcmeekin.info
    (reason: 550 Host unknown)
    (expanded from: <rrm3 at users.berlios.de>)

   ----- Transcript of session follows -----
550 5.1.2 viper at mcmeekin.info... Host unknown (Name server: mcmeekin.info: host not found)
-------------- next part --------------
An embedded message was scrubbed...
From: clc-devel at lists.berlios.de
Subject: [bug report] libgnomeprint2: missing dependency, cups.
Date: 17 Jan 2004 22:05:58 +0100
Size: 1283
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20040117/ded93667/attachment.mht>

From jw at tks6.net  Mon Jan 19 13:35:07 2004
From: jw at tks6.net (Johannes Winkelmann)
Date: Mon, 19 Jan 2004 14:35:07 +0100
Subject: [clc-devel] Returned mail: see transcript for details
In-Reply-To: <200401172106.i0HL62a28211@bat.berlios.de>
References: <200401172106.i0HL62a28211@bat.berlios.de>
Message-ID: <20040119133507.GB2407@hoc>

Hey,

On Sat, Jan 17, 2004 at 22:06:02 +0100, Mail Delivery Subsystem wrote:
> The original message was received at Sat, 17 Jan 2004 22:06:01 +0100
> from rfhs0023.fh-regensburg.de [194.95.104.23]
> 
>    ----- The following addresses had permanent fatal errors -----
> viper at mcmeekin.info
>     (reason: 550 Host unknown)
>     (expanded from: <rrm3 at users.berlios.de>)
> 
>    ----- Transcript of session follows -----
> 550 5.1.2 viper at mcmeekin.info... Host unknown (Name server: mcmeekin.info: host not found)

I figured I let this bug report through... there seems to be a problem
with mcmeekin.info from time to time (this is the 2nd return message).

Robert, and idea? ;-)

Johannes

(bug report notification follows)
> From: clc-devel at lists.berlios.de
> Date: 17 Jan 2004 22:05:58 +0100
> To: rrm3 at users.berlios.de
> Subject: [bug report] libgnomeprint2: missing dependency, cups.
> 
> Description: libgnomeprint2 requires cups installed to build.  This is not listed on the "#Depends on" field of the Pkgfile.
> 
> Contact: jack at tonkin.org.uk
> 
> User: anonymous
> 
> http://crux.fh-regensburg.de/cgi-bin/cvstrac/tktview?tn=28


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


From rrm3 at rrm3.org  Mon Jan 19 20:51:36 2004
From: rrm3 at rrm3.org (Robert McMeekin)
Date: Mon, 19 Jan 2004 15:51:36 -0500
Subject: [clc-devel] Returned mail: see transcript for details
In-Reply-To: <20040119133507.GB2407@hoc>
References: <200401172106.i0HL62a28211@bat.berlios.de>
	 <20040119133507.GB2407@hoc>
Message-ID: <1074545495.17007.18.camel@station.local>

Hey Johannes,

On Mon, 2004-01-19 at 08:35, Johannes Winkelmann wrote:
[...]
> I figured I let this bug report through... there seems to be a problem
> with mcmeekin.info from time to time (this is the 2nd return message).
> 
> Robert, and idea? ;-)

Yeah.  I don't think I own that domain anymore (I just looked at the
webview from my domains at dotster.com, and it's not listed).  I'd been
aware of this for a while, but no one was complaining and I'm pretty
lazy.  I'll see what I can do about this.  Thanks.  And I'll look at
libgnomeprint too.  ;-)

[...]
> > http://crux.fh-regensburg.de/cgi-bin/cvstrac/tktview?tn=28

On a somewhat related note, I've completely lost and forgotten how to
log in to tcvstrac on crux.fh-regensburg.de (So, Martin, you can expext
an email from me).
-- 
Robert McMeekin <rrm3 at rrm3.org>
http://web.rrm3.org/



From sip at varlock.com  Thu Jan 22 04:48:19 2004
From: sip at varlock.com (Simone Rota)
Date: Thu, 22 Jan 2004 05:48:19 +0100
Subject: [clc-devel] Freetye 2.1.7 issues
Message-ID: <1074746898.28654.17.camel@sip.linux>

Hi,

I found the new freetype (>=2.1.6) could break quite a number
of packages:
http://studio.imagemagick.org/pipermail/magick-bugs/2003-December/001573.html

I noticed the issue today while packaging fltk .Since the
include method for freetupe is changed, the ports should be upgraded
or patched.
Ie: possibly affected ports are imagemagick, wine.
Xft and related ports are a problem as well since xft it's linked to
freetype.

I only tested fltk and imagemagick, I can confirm that
on my machine freetype2/xft are dubbed unusable by the configure
scripts.

Quite a mess, uh?

Simone

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




From sip at varlock.com  Thu Jan 22 15:51:00 2004
From: sip at varlock.com (Simone Rota)
Date: Thu, 22 Jan 2004 16:51:00 +0100
Subject: [clc-devel] Freetye 2.1.7 issues
In-Reply-To: <1074746898.28654.17.camel@sip.linux>
References: <1074746898.28654.17.camel@sip.linux>
Message-ID: <1074786660.11127.5.camel@sip.linux>

On Thu, 2004-01-22 at 05:48, Simone Rota wrote:
> I only tested fltk and imagemagick, I can confirm that
> on my machine freetype2/xft are dubbed unusable by the configure
> scripts.

Uhm. You can notice the same issue trying to build pango,
or consequently gimp-devel:

In file included from pango-ot-private.h:25,
                 from pango-ot-info.c:22:
/usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h'
hasn't been included yet!"
/usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always
use macros to include FreeType header files."
/usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:"
/usr/include/freetype2/freetype/freetype.h:23:2: #error "  #include
<ft2build.h>"
/usr/include/freetype2/freetype/freetype.h:24:2: #error "  #include
FT_FREETYPE_H"
pango-ot-info.c:25:31: freetype/ftmodule.h: No such file or directory
make[3]: *** [pango-ot-info.lo] Error 1
make[3]: Leaving directory
`/usr/ports/opt/pango/work/src/pango-1.2.5/pango/opentype'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/usr/ports/opt/pango/work/src/pango-1.2.5/pango'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/ports/opt/pango/work/src/pango-1.2.5'
make: *** [all-recursive-am] Error 2
=======> ERROR: Building '/usr/ports/opt/pango/pango#1.2.5-1.pkg.tar.gz'
failed.

Should we revert to old freetype 2.1.5? Or patch all ports
with the damn'd ft2build.h include directive?

Regards,
Simone

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




From per at fukt.bth.se  Fri Jan 23 14:18:05 2004
From: per at fukt.bth.se (Per Liden)
Date: Fri, 23 Jan 2004 15:18:05 +0100 (CET)
Subject: [clc-devel] Freetye 2.1.7 issues
In-Reply-To: <1074746898.28654.17.camel@sip.linux>
References: <1074746898.28654.17.camel@sip.linux>
Message-ID: <Pine.LNX.4.58.0401231514590.2567@1-1-2-5a.f.sth.bostream.se>

On Thu, 22 Jan 2004, Simone Rota wrote:

> Hi,

Hi,

> I found the new freetype (>=2.1.6) could break quite a number
> of packages:
> http://studio.imagemagick.org/pipermail/magick-bugs/2003-December/001573.html
>
> I noticed the issue today while packaging fltk .Since the
> include method for freetupe is changed, the ports should be upgraded
> or patched.
> Ie: possibly affected ports are imagemagick, wine.
> Xft and related ports are a problem as well since xft it's linked to
> freetype.
>
> I only tested fltk and imagemagick, I can confirm that
> on my machine freetype2/xft are dubbed unusable by the configure
> scripts.
>
> Quite a mess, uh?

Hmm... damn. I got the impression that only private/internal header files
where renamed/changed. Obviously I was wrong.

I wouldn't mind going back to freetype 2.1.5 again to resolve this mess.

Comments?

/Per


From danm at gmx.li  Fri Jan 23 22:08:43 2004
From: danm at gmx.li (Daniel Mueller)
Date: Fri, 23 Jan 2004 23:08:43 +0100
Subject: [clc-devel] Freetye 2.1.7 issues
In-Reply-To: <Pine.LNX.4.58.0401231514590.2567@1-1-2-5a.f.sth.bostream.se>
References: <1074746898.28654.17.camel@sip.linux>
	<Pine.LNX.4.58.0401231514590.2567@1-1-2-5a.f.sth.bostream.se>
Message-ID: <20040123230843.1dfc4760@torax.danm.de>

On Fri, 23 Jan 2004 15:18:05 +0100 (CET)
Per Liden <per at fukt.bth.se> wrote:

> I wouldn't mind going back to freetype 2.1.5 again to resolve this
> mess.
> 
> Comments?
> 

------------snip-------------
--- /usr/include/freetype2/freetype/freetype.h.orig     2004-01-23
22:57:02.390297736 +0100+++ /usr/include/freetype2/freetype/freetype.h 
2004-01-23 22:58:43.289958656 +0100@@ -17,13 +17,12 @@
 
 
 #ifndef FT_FREETYPE_H
-#error "`ft2build.h' hasn't been included yet!"
-#error "Please always use macros to include FreeType header files."
-#error "Example:"
-#error "  #include <ft2build.h>"
-#error "  #include FT_FREETYPE_H"
+#ifndef FT_FREETYPE_H_OBSOLETE
+#define FT_FREETYPE_H_OBSOLETE
+#include <ft2build.h>
+#include FT_FREETYPE_H
+#endif
 #endif
-
 
 #ifndef __FREETYPE_H__
 #define __FREETYPE_H__
--------------snap--------------

Could this be a solution ? Any side effects ?

bye, danm

-- 
Daniel Mueller
Berlin, Germany		(OpenPGP:  1024D/126EC290)


From per at fukt.bth.se  Fri Jan 23 22:45:17 2004
From: per at fukt.bth.se (Per Liden)
Date: Fri, 23 Jan 2004 23:45:17 +0100 (CET)
Subject: [clc-devel] Freetye 2.1.7 issues
In-Reply-To: <20040123230843.1dfc4760@torax.danm.de>
References: <1074746898.28654.17.camel@sip.linux>
 <Pine.LNX.4.58.0401231514590.2567@1-1-2-5a.f.sth.bostream.se>
 <20040123230843.1dfc4760@torax.danm.de>
Message-ID: <Pine.LNX.4.58.0401232340510.4019@1-1-2-5a.f.sth.bostream.se>

On Fri, 23 Jan 2004, Daniel Mueller wrote:

> On Fri, 23 Jan 2004 15:18:05 +0100 (CET)
> Per Liden <per at fukt.bth.se> wrote:
>
> > I wouldn't mind going back to freetype 2.1.5 again to resolve this
> > mess.
> >
> > Comments?
> >
>
> ------------snip-------------
> --- /usr/include/freetype2/freetype/freetype.h.orig     2004-01-23
> 22:57:02.390297736 +0100+++ /usr/include/freetype2/freetype/freetype.h
> 2004-01-23 22:58:43.289958656 +0100@@ -17,13 +17,12 @@
>
>
>  #ifndef FT_FREETYPE_H
> -#error "`ft2build.h' hasn't been included yet!"
> -#error "Please always use macros to include FreeType header files."
> -#error "Example:"
> -#error "  #include <ft2build.h>"
> -#error "  #include FT_FREETYPE_H"
> +#ifndef FT_FREETYPE_H_OBSOLETE
> +#define FT_FREETYPE_H_OBSOLETE
> +#include <ft2build.h>
> +#include FT_FREETYPE_H
> +#endif
>  #endif
> -
>
>  #ifndef __FREETYPE_H__
>  #define __FREETYPE_H__
> --------------snap--------------
>
> Could this be a solution ? Any side effects ?

Nice idea, but I'm afraid it's not enough. For example, building pango
still fails with:

...
/bin/sh ../../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../..
-DPANGO_ENABLE_ENGINE -DSYSCONFDIR=\"/usr/etc\" -DLIBDIR=\"/usr/lib\"
-DG_DISABLE_DEPRECATED -DG_DISABLE_CAST_CHECKS -pthread
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/freetype2 -I/usr/X11R6/include -I../..    -O2 -march=i686
-pipe -Wall -c pango-ot-info.c
 gcc -DHAVE_CONFIG_H -I. -I. -I../.. -DPANGO_ENABLE_ENGINE
-DSYSCONFDIR=\"/usr/etc\" -DLIBDIR=\"/usr/lib\" -DG_DISABLE_DEPRECATED
-DG_DISABLE_CAST_CHECKS -pthread -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/X11R6/include
-I../.. -O2 -march=i686 -pipe -Wall -c pango-ot-info.c  -fPIC -DPIC -o
.libs/pango-ot-info.o
pango-ot-info.c:25:31: freetype/ftmodule.h: No such file or directory
make[3]: *** [pango-ot-info.lo] Error 1
make[3]: Leaving directory
`/home/per/crux/cvs/ports/opt/pango/work/src/pango-1.2.5/pango/opentype'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/per/crux/cvs/ports/opt/pango/work/src/pango-1.2.5/pango'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/per/crux/cvs/ports/opt/pango/work/src/pango-1.2.5'
make: *** [all-recursive-am] Error 2


I'll just go back to 2.1.5 for now. Let's hope 2.1.8 will have better
"compatability glue" or something...

/Per


From dkg at con-fuse.org  Tue Jan 27 22:16:18 2004
From: dkg at con-fuse.org (Daniel K. Gebhart)
Date: Tue, 27 Jan 2004 23:16:18 +0100
Subject: [clc-devel] Im back -- access to clc cvs.
Message-ID: <20040127221618.GA21647@sperrstunde.at>

Hi,

 Nice to be back again. My new machine is now on air and it's running
CRUX-1.3 (kernel 2.6.1). Since my old machine is crashed and I have a new
box now, my ssh-key has changed. My new rsa key now:

ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAIEA612H+kJHDxNtFFJm8plIKqTZkZTT/n1GYEEJ15upczc/Jo/SMheb5qjKxzXmCTbIZ8ZQwLU3Du9hcF3L3vMeYdPjbPtzH+9eBdsKJg9KNJ34tLFXbFoX2Edq6tmEf54IzWqp0Q4E9cYBkwd89l8JNaccXhj4uy5B57PYS1VLmiM=
dkg at moron

 Would be nice if someone (obbl?) could add this one to authorized_keys so
that I'll be able to contribute to CLC again.

Thanks and good nite,
 daniel

-- 
Daniel K. Gebhart                               http://dkg.con-fuse.org/
Institute for Computer Science                   University of Innsbruck
Fon: (office): +43 512 507 6444     Mail: <daniel.gebhart(at)uibk.ac.at>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20040127/4afa0188/attachment.asc>

From dkg at con-fuse.org  Wed Jan 28 16:36:53 2004
From: dkg at con-fuse.org (Daniel K. Gebhart)
Date: Wed, 28 Jan 2004 17:36:53 +0100
Subject: [clc-devel] mozilla2 footprint mismatch
Message-ID: <20040128163653.GD31803@sperrstunde.at>

Hi,

=======> ERROR: Footprint mismatch found:
MISSING   lrwxrwxrwx      root/root       usr/lib/libmozjs.so ->
libmozjs.so
MISSING   lrwxrwxrwx      root/root       usr/lib/libnspr4.so ->
libnspr4.so
MISSING   lrwxrwxrwx      root/root       usr/lib/libnss3.so -> libnss3.so
MISSING   lrwxrwxrwx      root/root       usr/lib/libplc4.so -> libplc4.so
MISSING   lrwxrwxrwx      root/root       usr/lib/libplds4.so ->
libplds4.so
MISSING   lrwxrwxrwx      root/root       usr/lib/libsmime3.so ->
libsmime3.so
MISSING   lrwxrwxrwx      root/root       usr/lib/libsoftokn3.so ->
libsoftokn3.so
MISSING   lrwxrwxrwx      root/root       usr/lib/libssl3.so -> libssl3.so
NEW       lrwxrwxrwx      root/root       usr/lib/libmozjs.so ->
mozilla/libmozjs.so
NEW       lrwxrwxrwx      root/root       usr/lib/libnspr4.so ->
mozilla/libnspr4.so
NEW       lrwxrwxrwx      root/root       usr/lib/libnss3.so ->
mozilla/libnss3.so
NEW       lrwxrwxrwx      root/root       usr/lib/libplc4.so ->
mozilla/libplc4.so
NEW       lrwxrwxrwx      root/root       usr/lib/libplds4.so ->
mozilla/libplds4.so
NEW       lrwxrwxrwx      root/root       usr/lib/libsmime3.so ->
mozilla/libsmime3.so
NEW       lrwxrwxrwx      root/root       usr/lib/libsoftokn3.so ->
mozilla/libsoftokn3.so
NEW       lrwxrwxrwx      root/root       usr/lib/libssl3.so ->
mozilla/libssl3.so
=======> ERROR: Building
'/usr/ports/contrib/mozilla2/mozilla2#1.6-2.pkg.tar.gz' failed.

please fix.

peace, daniel

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


From rrm3 at rrm3.org  Wed Jan 28 17:30:47 2004
From: rrm3 at rrm3.org (Robert McMeekin)
Date: Wed, 28 Jan 2004 12:30:47 -0500 (EST)
Subject: [clc-devel] mozilla2 footprint mismatch
In-Reply-To: <20040128163653.GD31803@sperrstunde.at>
References: <20040128163653.GD31803@sperrstunde.at>
Message-ID: <200401281730.i0SHUkr1011723@reveal.local>

Sorry about that.  I've got this phobia, you see.  I'm afraid if I build 
mozilla one more time, my computer will go up in smoke and flames.  ;-)

On Wed, 28 Jan 2004 at 17:36:53 +0100,
dkg[at]con-fuse.org (Daniel Gebhart) wrote:
[...]
> =======> ERROR: Footprint mismatch found:
> MISSING   lrwxrwxrwx      root/root       usr/lib/libmozjs.so -> libmozjs.so
> MISSING   lrwxrwxrwx      root/root       usr/lib/libnspr4.so -> libnspr4.so
> MISSING   lrwxrwxrwx      root/root       usr/lib/libnss3.so -> libnss3.so
> MISSING   lrwxrwxrwx      root/root       usr/lib/libplc4.so -> libplc4.so
> MISSING   lrwxrwxrwx      root/root       usr/lib/libplds4.so -> libplds4.so
> MISSING   lrwxrwxrwx      root/root       usr/lib/libsmime3.so -> libsmime3.so
> MISSING   lrwxrwxrwx      root/root       usr/lib/libsoftokn3.so -> libsoftokn3.so
> MISSING   lrwxrwxrwx      root/root       usr/lib/libssl3.so -> libssl3.so
> NEW       lrwxrwxrwx      root/root       usr/lib/libmozjs.so -> mozilla/libmozjs.so
> NEW       lrwxrwxrwx      root/root       usr/lib/libnspr4.so -> mozilla/libnspr4.so
> NEW       lrwxrwxrwx      root/root       usr/lib/libnss3.so -> mozilla/libnss3.so
> NEW       lrwxrwxrwx      root/root       usr/lib/libplc4.so -> mozilla/libplc4.so
> NEW       lrwxrwxrwx      root/root       usr/lib/libplds4.so -> mozilla/libplds4.so
> NEW       lrwxrwxrwx      root/root       usr/lib/libsmime3.so -> mozilla/libsmime3.so
> NEW       lrwxrwxrwx      root/root       usr/lib/libsoftokn3.so -> mozilla/libsoftokn3.so
> NEW       lrwxrwxrwx      root/root       usr/lib/libssl3.so -> mozilla/libssl3.so
> =======> ERROR: Building
> '/usr/ports/contrib/mozilla2/mozilla2#1.6-2.pkg.tar.gz' failed.

// Rob
-- 
"He's an impetuous Republican librarian in drag. She's an orphaned
 impetuous Valkyrie from a different time and place. They fight crime!"
 



From hussy at sysop.nu  Wed Jan 28 23:14:24 2004
From: hussy at sysop.nu (Hussy)
Date: Thu, 29 Jan 2004 00:14:24 +0100
Subject: [clc-devel] mozilla2 footprint mismatch
References: <20040128163653.GD31803@sperrstunde.at> <200401281730.i0SHUkr1011723@reveal.local>
Message-ID: <001801c3e5f4$78701c60$0477a8c0@C3PO>

Go to the dir of mozilla2 ( /usr/ports/contrib/mozilla2 )
and do: pkgmk -uf <-- Update Footprint
this will update the footprint, and you should be able to
install mozilla2.

Good Luck // Henrik



----- Original Message -----
From: "Robert McMeekin" <rrm3 at rrm3.org>
To: <clc-devel at lists.berlios.de>
Sent: Wednesday, January 28, 2004 6:30 PM
Subject: Re: [clc-devel] mozilla2 footprint mismatch


> Sorry about that.  I've got this phobia, you see.  I'm afraid if I build
> mozilla one more time, my computer will go up in smoke and flames.  ;-)
>
> On Wed, 28 Jan 2004 at 17:36:53 +0100,
> dkg[at]con-fuse.org (Daniel Gebhart) wrote:
> [...]
> > =======> ERROR: Footprint mismatch found:
> > MISSING   lrwxrwxrwx      root/root       usr/lib/libmozjs.so ->
libmozjs.so
> > MISSING   lrwxrwxrwx      root/root       usr/lib/libnspr4.so ->
libnspr4.so
> > MISSING   lrwxrwxrwx      root/root       usr/lib/libnss3.so ->
libnss3.so
> > MISSING   lrwxrwxrwx      root/root       usr/lib/libplc4.so ->
libplc4.so
> > MISSING   lrwxrwxrwx      root/root       usr/lib/libplds4.so ->
libplds4.so
> > MISSING   lrwxrwxrwx      root/root       usr/lib/libsmime3.so ->
libsmime3.so
> > MISSING   lrwxrwxrwx      root/root       usr/lib/libsoftokn3.so ->
libsoftokn3.so
> > MISSING   lrwxrwxrwx      root/root       usr/lib/libssl3.so ->
libssl3.so
> > NEW       lrwxrwxrwx      root/root       usr/lib/libmozjs.so ->
mozilla/libmozjs.so
> > NEW       lrwxrwxrwx      root/root       usr/lib/libnspr4.so ->
mozilla/libnspr4.so
> > NEW       lrwxrwxrwx      root/root       usr/lib/libnss3.so ->
mozilla/libnss3.so
> > NEW       lrwxrwxrwx      root/root       usr/lib/libplc4.so ->
mozilla/libplc4.so
> > NEW       lrwxrwxrwx      root/root       usr/lib/libplds4.so ->
mozilla/libplds4.so
> > NEW       lrwxrwxrwx      root/root       usr/lib/libsmime3.so ->
mozilla/libsmime3.so
> > NEW       lrwxrwxrwx      root/root       usr/lib/libsoftokn3.so ->
mozilla/libsoftokn3.so
> > NEW       lrwxrwxrwx      root/root       usr/lib/libssl3.so ->
mozilla/libssl3.so
> > =======> ERROR: Building
> > '/usr/ports/contrib/mozilla2/mozilla2#1.6-2.pkg.tar.gz' failed.
>
> // Rob
> --
> "He's an impetuous Republican librarian in drag. She's an orphaned
>  impetuous Valkyrie from a different time and place. They fight crime!"
>
>
> _______________________________________________
> clc-devel mailing list
> clc-devel at lists.berlios.de
> http://lists.berlios.de/mailman/listinfo/clc-devel
>



From jw at tks6.net  Fri Jan 30 08:45:15 2004
From: jw at tks6.net (Johannes Winkelmann)
Date: Fri, 30 Jan 2004 09:45:15 +0100
Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link
In-Reply-To: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de>
References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de>
Message-ID: <20040130084515.GA946@hoc>

Hey, 

Simone brought up an interesting point:

On Fri, Jan 30, 2004 at 05:58:45 +0100, clc-devel at berlios.de wrote:
> Description: Should the plugin link for j2sdk be moved into
> /usr/lib/firebird/plugins, since its the default browser?
Note: j2sdk still creates a symlink in /usr/lib/mozilla/plugins.


> Another option is to separate the ports (see firebird-acroread-plugin).
Well, this could be an option :-) Certainly looks cool.

I know that J?rgen's j2re Port creates a symlink for firebird, so I'm
wondering whether we should drop this from j2sdk completely and use j2re
for plugin functionality.

Another problem is that I can't find public downloads for J2SE (j2sdk),
and I was wondering what to do about this... should we use blackdown's
JDK (which is based on Sun's JDK) exclusively, or provide an up to date
port without download possibility?

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


From tillbiedermann at yahoo.de  Fri Jan 30 23:48:53 2004
From: tillbiedermann at yahoo.de (Till Biedermann)
Date: Sat, 31 Jan 2004 00:48:53 +0100
Subject: [clc-devel] ports-database at tbmnet.de
Message-ID: <1075506533.9115.19.camel@Horst.wg.lan>

hi

this evening i had a little bit of time to push my ports-database to the
next level of usability.

http://www.tbmnet.de/tbmnet.php?content=crux_ports_database

the updating of existing repositories is very easy now. i set a password
for this function to prevent that everybody klicks the button to see
what might happen.

i also found the bug why the unmaintained repositiory could not be
updated.
now the script checks the existance of every file before trying to open
it and outputs an error message if a file is missing.

last thing: in the first version i forgot the possibility that ports can
be removed from a repository. now the script detects which ports are not
in the repository anymore and removes it from the database.

improvement suggestions are wellcome.

regards till
-- 
http://www.tbmnet.de



From sip at varlock.com  Sat Jan 31 18:16:33 2004
From: sip at varlock.com (Simone Rota)
Date: Sat, 31 Jan 2004 19:16:33 +0100
Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin
 link
In-Reply-To: <20040130084515.GA946@hoc>
References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc>
Message-ID: <401BF101.6090007@varlock.com>

On 01/30/04 09:45 Johannes Winkelmann wrote:

> I know that J?rgen's j2re Port creates a symlink for firebird, so I'm
> wondering whether we should drop this from j2sdk completely and use j2re
> for plugin functionality.

I'll maintain both the firebird-jre-plugin and firebird-jsdk-plugin,
since it's a trivial task, as soon as we decide what to do regarding
the following point.

> Another problem is that I can't find public downloads for J2SE (j2sdk),
> and I was wondering what to do about this... should we use blackdown's
> JDK (which is based on Sun's JDK) exclusively, or provide an up to date
> port without download possibility?

Anyone has some direct experience and can compare the two versions
regarding firebird/mozilla compatibility, general speed and stability?
If blackdown performs well I could personally live with
a slightly outdated release; other opinions?

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