From jw at tks6.net Wed Sep 1 12:38:58 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Wed, 1 Sep 2004 14:38:58 +0200 Subject: [clc-devel] Applying to be a package maintainer In-Reply-To: <1093971453.31482.43.camel@emptyness> References: <1093819876.17717.17.camel@emptyness> <20040830100556.GA25668@hoc> <1093971453.31482.43.camel@emptyness> Message-ID: <20040901123858.GA32065@hoc> Hi Anthony, On Tue, Aug 31, 2004 at 09:57:32 -0700, Anthony de Almeida Lopes wrote: > Oops thought I sent this to the list too... > > Alright, let me qualify first before I talk about ports. For the last 3 > months I've been using my own > distribution of Linux made. [..?] > I have a preliminary port of gcc-ssp here: > http://sonic.net/~someone/files/gcc-ssp.tar.bz2 > It's not finished right now, I'd advise against using it with ccache > right now, although I do use it for everything it needs some more > testing. > > The other thing I'm interest in porting right now is gaim-encryption > (see: http://gaim-encryption.sourceforge.net) which is just a method of > encrypting conversation over AOL's instant messaging network via gaim > (see http://gaim.sourceforge.net), a very popular IM client for Linux. I'd suggest you set up a personal ports repository and start to maintain those ports for a while. This might be one of the points where our maintainer guidelines are unclear, but for now we try to select maintainers which have some experience with maintainance of CRUX ports and CRUX in general. While you seem qualified to reach that, we can hardly judge your capabilities by a single port you call preliminary, and ideas for ports you'd like to do. I also had the impression that you just started with CRUX. A few notes on your port: - the header should only contain a single URL tag - there are some files missing in your source line: - protector.dif - protectoronly.dif - protector.c and protector.h - ccache-gcc-ssp ccache-g++-ssp Fixing the later will allow you to refer to those file using a correct path; for now, your Pkgfile accesses files outside the work directory of a port, which will fail if the pkgmk work directory is different from the port's base directory. Furthermore, I'm not sure if it it's possible to have source files in a directory, but this is of course easily changed. So please continue to build ports, publish them and maintain them for a while, and once you're familiar with CRUX and the things surrounding it (CLC etc.) feel free to apply again here. If you have further questions, feel free to ask; there's also an IRC channel where many of the guys from CLC can be found: it's #crux on irc.freenode.net. Kind regards, Johannes P.S. Please don't CC me when replying to the list -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From jw at tks6.net Wed Sep 1 13:23:34 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Wed, 1 Sep 2004 15:23:34 +0200 Subject: [clc-devel] RFC: wrapper for ccache and distcc Message-ID: <20040901132334.GC32065@hoc> Hi, A work collegue of mine brought to my attention that building tcl fails when using ccache, and I realized that the error is quite simple (not to say stupid ;-)); ccache comes with wrappers for gcc and g++ which just call 'ccache gcc $*' or 'ccache g++ $*'. Unfortunately this creates a problem when the Makefile calls the wrapper like this: ccache-gcc [...] -DTCL_WIDE_INT_TYPE=long\ long Since the wrapper is a shell script and will call ccache gcc $* This will break the last argument into two ("-DTCL_WIDE_INT_TYPE=long" and "long"). Maybe there's a way to work around that, but I wouldn't know about it. This e.g. breaks tcl, and I remember it also broke gimp < 2 (not sure about >= 2). Anyway, if ccache (the application) is called as gcc (by renaming it or creating a symlink called 'gcc'), it works fine. The additional advantage of this is that even if a Makefile doesn't use the CC and CXX variables, this will work. The problem (and reason why I didn't do it like this earlier) is that those symlinks must be put somewhere, and I'm not sure what the right place is; IMO it should be something which isn't in the path usually, which means that /bin shouldn't even be considered. gentoo uses /usr/lib/bin/{gcc,cc,g++,c++}, not sure what others use. Are there any suggestions what might be a good path for CRUX? Kind regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From vector at pp.nic.fi Wed Sep 1 14:15:01 2004 From: vector at pp.nic.fi (Jukka Heino) Date: Wed, 1 Sep 2004 17:15:01 +0300 (EEST) Subject: [clc-devel] RFC: wrapper for ccache and distcc Message-ID: <28227648.1094048101277.JavaMail.vector@pp.nic.fi> > Hi, > > A work collegue of mine brought to my attention that building tcl fails > when using ccache, and I realized that the error is quite simple (not to > say stupid ;-)); ccache comes with wrappers for gcc and g++ which just > call 'ccache gcc $*' or 'ccache g++ $*'. Unfortunately this creates a > problem when the Makefile calls the wrapper like this: > ccache-gcc [...] -DTCL_WIDE_INT_TYPE=long\ long I might be wrong, but wouldn't changing $* to "$@" (notice the quotes) fix the problem? I had a similar problem with soapbox before. // Jukka From jw at tks6.net Wed Sep 1 14:35:09 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Wed, 1 Sep 2004 16:35:09 +0200 Subject: [clc-devel] RFC: wrapper for ccache and distcc In-Reply-To: <28227648.1094048101277.JavaMail.vector@pp.nic.fi> References: <28227648.1094048101277.JavaMail.vector@pp.nic.fi> Message-ID: <20040901143509.GA1958@hoc> Hey, On Wed, Sep 01, 2004 at 17:15:01 +0300, Jukka Heino wrote: > >Hi, > > > >A work collegue of mine brought to my attention that building tcl fails > >when using ccache, and I realized that the error is quite simple (not to > >say stupid ;-)); ccache comes with wrappers for gcc and g++ which just > >call 'ccache gcc $*' or 'ccache g++ $*'. Unfortunately this creates a > >problem when the Makefile calls the wrapper like this: > > ccache-gcc [...] -DTCL_WIDE_INT_TYPE=long\ long > > I might be wrong, but wouldn't changing $* to "$@" (notice the quotes) > fix the problem? I had a similar problem with soapbox before. Indeed, that works! I tried "$*" before but this wouldn't work... thanks for the tip, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From victord at v600.net Wed Sep 1 16:07:34 2004 From: victord at v600.net (Victor) Date: Wed, 01 Sep 2004 12:07:34 -0400 Subject: [clc-devel] Rsync for Maintainers In-Reply-To: <20040830072912.GA23878@hoc> References: <412EC566.3040802@v600.net> <20040830072912.GA23878@hoc> Message-ID: <4135F3C6.2050203@v600.net> Johannes Winkelmann wrote: > Hi, > [snip] > > Advantages: > - Changes are transmitted using diffs (httpup: whole files) Well, also clients don't have to run any servers at all. There is a central location for all the ports (fewer downtime with people rebooting their boxes, not everyone has dedicated servers) > Disadvantages: > - Requires running a service (rsyncd) Yeah, but on the server > - Configurations looks rather complicated It's not really :) > - If a repo maintainer decides to just not update his repo anymore, we > have to detect that he's not accessing our repo anymore; this is a bit > harder in a "push" model than it is in a "pull" model (as the httpup > ideas implement). Yeah, that's an issue... How is it solved now? > - To merge those ports into one collection, you'll need another script > (I don't think rsync does this); therefore, you'll end up with more > components to maintain (rsync, script), which run independently, which > means that you have to manually ensure that there are no "commits" to > the collection while merging it (I know this is simple to do, but it > will cause some disk load). Actually, I didn't think we would merge them into one collection. -Victor From ncrfgs at tin.it Wed Sep 1 18:46:44 2004 From: ncrfgs at tin.it (ncrfgs) Date: Wed, 1 Sep 2004 20:46:44 +0200 Subject: [clc-devel] unmaintained/lm_sensors: Port update Message-ID: <20040901184644.GA2573@ncrfgs3.ncrfgs> With the Linux 2.6.x series, lm_sensor' kernel space code was include into the kernel and after CRUX switched to Linux kernel 2.6.x series, lm_sensors port' "README" and "post-install" files became useless and the the following line can be safely deleted from the "Pkgfile" script. rm -f $PKG/lib/modules/`uname -r`/modules* A possible patch is attached to this message. http://clc.morpheus.net:6999/clc/tktview?tn=11 Best regards. -- Value your freedom, or you will lose it, teaches history. ``Don't bother us with politics,'' respond those who don't want to learn. -- Richard M. Stallman http://www.gnu.org/philosophy/linux-gnu-freedom.html -------------- next part -------------- diff -Nru lm_sensors.orig/Pkgfile lm_sensors/Pkgfile --- lm_sensors.orig/Pkgfile 2004-08-17 22:01:44.000000000 +0200 +++ lm_sensors/Pkgfile 2004-09-01 20:34:17.368443264 +0200 @@ -6,7 +6,7 @@ name=lm_sensors version=2.8.7 -release=1 +release=2 source=(http://www2.lm-sensors.nu/~lm78/archive/$name-$version.tar.gz) build () { @@ -14,7 +14,5 @@ make user PREFIX=/usr make PREFIX=$PKG/usr ETCDIR=$PKG/etc user_install - rm -f $PKG/usr/include/linux/i2c-dev.h - rm -f $PKG/lib/modules/`uname -r`/modules* + rm $PKG/usr/include/linux/i2c-dev.h } - diff -Nru lm_sensors.orig/README lm_sensors/README --- lm_sensors.orig/README 2004-08-17 22:01:44.000000000 +0200 +++ lm_sensors/README 1970-01-01 01:00:00.000000000 +0100 @@ -1,15 +0,0 @@ -README for lm_sensors - -REQUIREMENTS - -PRE-INSTALL - -INSTALL -- You will get footprint mismatches because of the kernel modules - that are installed. Don't worry ;) - -POST-INSTALL -- Run the post-install script to update the module dependency files. - -PRECAUTION -- Put your kernel sources to /usr/src/linux-version diff -Nru lm_sensors.orig/post-install lm_sensors/post-install --- lm_sensors.orig/post-install 2004-08-17 22:01:44.000000000 +0200 +++ lm_sensors/post-install 1970-01-01 01:00:00.000000000 +0100 @@ -1,4 +0,0 @@ -#!/bin/bash - -depmod -a - -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jw at tks6.net Wed Sep 1 19:39:23 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Wed, 1 Sep 2004 21:39:23 +0200 Subject: [clc-devel] Rsync for Maintainers In-Reply-To: <4135F3C6.2050203@v600.net> References: <412EC566.3040802@v600.net> <20040830072912.GA23878@hoc> <4135F3C6.2050203@v600.net> Message-ID: <20040901193923.GA18605@hoc> Hi, On Wed, Sep 01, 2004 at 12:07:34 -0400, Victor wrote: > Johannes Winkelmann wrote: > >Hi, > > > [snip] > > > >Advantages: > >- Changes are transmitted using diffs (httpup: whole files) > > Well, also clients don't have to run any servers at all. I mentioned that in the difference section; this is both advantage and disadvantage; if you want an httpup repo, this solution would duplicate your work; furthermore and you can't develop independently. I'm not saying that distributed development is better, but I'm not convinced that centralized development is. Note that if you join CLC, you don't need a repo :-) > There is a central location for all the ports (fewer downtime with > people rebooting their boxes, not everyone has dedicated servers) Okay, I guess I wasn't too clear. Both suggestions I made would be hosted on a central server as well. Central access, but distributed (= independent) development. Illustration of the 'people collection' idea: +--------------------------------- | central server | | +--------------+ sync +----------------------+ + httpup repos + -------------> + separate collections + +--------------+ n 1 +----------------------+ ^ | | possible to subscribe directly | - merge into one collection | to prefer a repo over base/opt/ | - check duplicates contrib, or if you don't want | - rm base/opt/contrib dups | everything from people | - whatever checks you want | | - notifications | | V +------+ fetches +----------------------------+ + User + <-------------- + httpup collection 'people' + <-> Mirrors +------+ n 1 +----------------------------+ | | | +-------------------------------------- Note that this even allows maintainers of private repos to have duplicates over base/opt/contrib (my former mail said that such duplicates would cause a notification, coupled with the request to remove it); they just won't be propagated to the 'people' collection. Users can still get those by subscribing to the repo directly, and putting it higher in prt-get.conf than /usr/ports/people. At the same time, people who have dups over ports from base/opt/contrib don't have to maintain two httpup repos. I guess there is a need for a better explanation; I'll try to put it together sometime soon. > >- If a repo maintainer decides to just not update his repo anymore, we > > have to detect that he's not accessing our repo anymore; this is a bit > > harder in a "push" model than it is in a "pull" model (as the httpup > > ideas implement). > > Yeah, that's an issue... How is it solved now? the sync script updates the collections on the central server hourly (or whatever interval we'll choose). If there's a 404, we'll find out instantly. If we want to introduce checking for changes, this can be implemented in this update script. > >- To merge those ports into one collection, you'll need another script > > (I don't think rsync does this); therefore, you'll end up with more > > components to maintain (rsync, script), which run independently, which > > means that you have to manually ensure that there are no "commits" to > > the collection while merging it (I know this is simple to do, but it > > will cause some disk load). > > Actually, I didn't think we would merge them into one collection. Okay, but you need to check for duplicates, right? Unless you do that, it'll always be a number of independent repos, thus the quality won't improve which is one of my main goals. Regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From sip at varlock.com Wed Sep 1 20:57:53 2004 From: sip at varlock.com (Simone Rota) Date: Wed, 01 Sep 2004 22:57:53 +0200 Subject: [clc-devel] clcbuild results Message-ID: <413637D1.60008@varlock.com> Hi all, I had a couple of uber-outdated machines, so I re-run the infamous clcbuild script to get some binary package. Results at the same old place[1], as usual some failed port are my fault, known issues, etc. Regards, Simone [1] http://www.varlock.com/clcbuild -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From jw at tks6.net Thu Sep 2 08:11:01 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Thu, 2 Sep 2004 10:11:01 +0200 Subject: [clc-devel] clcbuild results In-Reply-To: <413637D1.60008@varlock.com> References: <413637D1.60008@varlock.com> Message-ID: <20040902081101.GB3800@hoc> Hi Simone, On Wed, Sep 01, 2004 at 22:57:53 +0200, Simone Rota wrote: > Hi all, > > I had a couple of uber-outdated machines, so I re-run > the infamous clcbuild script to get some binary package. > > Results at the same old place[1], as usual some > failed port are my fault, known issues, etc. Welcome back and thanks for running the tests again. Did you use pkg-get to install those packages? I was wondering whether we could create a very small install ISO containing just the base packages plus stuff you need to get your network up, and a way to directly fetch binary packages using pkg-get. I'd assume that this would be interesting for both those that want a minimal setup and those that want to setup a KDE/GNOME desktop without compiling everything or download CRUX Evolution which contains one DE too much for most people ;-). Just an idea though, didn't put a lot of thought into it. To think a bit ahead, it would be cool to select some packages on one machine and have a script download those binary package and build a customized install ISO from it, using the binary packages. Imagine: "Oh, I want base, X11, firefox, KDE and OpenOffice. Go!", and the next thing you remember is the CD tray opening and a shiny custom installation CD smiling at you. Oh well, I don't really think there's a real need for this, I was just carried away by the possibilites ;-) Regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From sip at varlock.com Thu Sep 2 08:55:13 2004 From: sip at varlock.com (Simone Rota) Date: Thu, 02 Sep 2004 10:55:13 +0200 Subject: [clc-devel] clcbuild results In-Reply-To: <20040902081101.GB3800@hoc> References: <413637D1.60008@varlock.com> <20040902081101.GB3800@hoc> Message-ID: <4136DFF1.8060803@varlock.com> On 09/02/04 10:11 Johannes Winkelmann wrote: > Hi Simone, Hi Johannes, > On Wed, Sep 01, 2004 at 22:57:53 +0200, Simone Rota wrote: > >>I had a couple of uber-outdated machines, so I re-run >>the infamous clcbuild script to get some binary package. > Welcome back and thanks for running the tests again. Did you use pkg-get > to install those packages? Actually I'm so lazy I didn't updated the machines yet :) But yes, I'm going to use pkg-get since I have 2 pkg-get-only machines, and previous runs have been very useful for detecting the most outstanding bugs. > I was wondering whether we could create a > very small install ISO containing just the base packages plus stuff you > need to get your network up, and a way to directly fetch binary packages > using pkg-get. I'd assume that this would be interesting for both those > that want a minimal setup and those that want to setup a KDE/GNOME > desktop without compiling everything or download CRUX Evolution which > contains one DE too much for most people ;-). Just an idea though, > didn't put a lot of thought into it. I agree (after all one of the reasons I'm trying to write some code with clcbuild & pkg-get is binary availability). Besides I think everybody installing CRUX on a new machine these days can realize that many binaries from the official cd are out of date, and having to wait such a long time to have an up-to-date machine is sometime a bit painful (for the ones always in a hurry). I personally like the way CRUX releases are managed by Per:no need to release once a month, just put out a new version where there is relevant new stuff or abi changes. An addon to quickly keep up with updates would be useful in many circumstances. > To think a bit ahead, it would be cool to select some packages on one > machine and have a script download those binary package and build a > customized install ISO from it, using the binary packages. Imagine: "Oh, > I want base, X11, firefox, KDE and OpenOffice. Go!", and the next thing > you remember is the CD tray opening and a shiny custom installation CD > smiling at you. > > Oh well, I don't really think there's a real need for this, I was just > carried away by the possibilites ;-) Maybe we're flying to high here, but since we're on topic I think it's an interesting idea; I suppose the main problem would be dependency handling at setup time, but I'd maintain the current setup and add contrib packages in a second time with the provided tool. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From jw at tks6.net Thu Sep 2 17:03:27 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Thu, 2 Sep 2004 19:03:27 +0200 Subject: [clc-devel] unmaintained/lm_sensors: Port update In-Reply-To: <20040901184644.GA2573@ncrfgs3.ncrfgs> References: <20040901184644.GA2573@ncrfgs3.ncrfgs> Message-ID: <20040902170327.GA21215@hoc> Hi, On Wed, Sep 01, 2004 at 20:46:44 +0200, ncrfgs wrote: > With the Linux 2.6.x series, lm_sensor' kernel space code was include into the > kernel and after CRUX switched to Linux kernel 2.6.x series, lm_sensors port' > "README" and "post-install" files became useless and the the following line can > be safely deleted from the "Pkgfile" script. > > rm -f $PKG/lib/modules/`uname -r`/modules* > > A possible patch is attached to this message. Applied, thanks. Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From ncrfgs at tin.it Fri Sep 3 12:21:27 2004 From: ncrfgs at tin.it (ncrfgs) Date: Fri, 3 Sep 2004 14:21:27 +0200 Subject: [clc-devel] unmaintained/fbset: Cosmetic changes Message-ID: <20040903122041.GA10185@ncrfgs3.ncrfgs> One of the I like about Crux packages management system is that allows build script to be clean and simple. If they are not it's a pity. =) A possible patch is attached to this message. Best regards. -- Value your freedom, or you will lose it, teaches history. ``Don't bother us with politics,'' respond those who don't want to learn. -- Richard M. Stallman http://www.gnu.org/philosophy/linux-gnu-freedom.html -------------- next part -------------- diff -Nru fbset.orig/Pkgfile fbset/Pkgfile --- fbset.orig/Pkgfile 2004-08-17 22:01:43.000000000 +0200 +++ fbset/Pkgfile 2004-09-03 11:56:27.466230896 +0200 @@ -5,17 +5,16 @@ name=fbset version=2.1 -release=1 -source=( - http://home.tvd.be/cr26864/Linux/fbdev/fbset-$version.tar.gz -) -build () { - cd $name-$version; - sed 's,/dev/fb,/dev/fb/,g' fbset.c > fbset.c.sed && \mv fbset.c.sed fbset.c - sed 's,/dev/fb,/dev/fb/,g' fbset.8 > fbset.8.set && \mv fbset.8.set fbset.8 +release=2 +source=(http://home.tvd.be/cr26864/Linux/fbdev/$name-$version.tar.gz) + +build() { + cd $name-$version + sed -i 's,/dev/fb,/dev/fb/,g' fbset.c + sed -i 's,/dev/fb,/dev/fb/,g' fbset.8 make - mkdir -p "$PKG/usr/bin" "$PKG/usr/man/man8" "$PKG/usr/man/man5" - cp fbset "$PKG/usr/bin"; - cp fb.modes.5 "$PKG/usr/man/man5" - cp fbset.8 "$PKG/usr/man/man8" + mkdir -p $PKG/usr/bin $PKG/usr/man/man{5,8} + install -m 755 fbset $PKG/usr/bin + install -m 644 fb.modes.5 $PKG/usr/man/man5 + install -m 644 fbset.8 $PKG/usr/man/man8 } -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jw at tks6.net Tue Sep 7 09:44:23 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Tue, 7 Sep 2004 11:44:23 +0200 Subject: [clc-devel] Ports to pick up... Message-ID: <20040907094423.GB10172@hoc> Hi, I'm planning to get rid of subversion-perl and subversion-python and swig (which I only maintained since the other two depend on it). I anyone's interested, feel free to pick them up. I'll tag them unmaintained for now... Regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From jw at tks6.net Tue Sep 7 09:52:08 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Tue, 7 Sep 2004 11:52:08 +0200 Subject: [clc-devel] Ports to pick up... In-Reply-To: <20040907094423.GB10172@hoc> References: <20040907094423.GB10172@hoc> Message-ID: <20040907095208.GC10172@hoc> On Tue, Sep 07, 2004 at 11:44:23 +0200, Johannes Winkelmann wrote: > Hi, > > I'm planning to get rid of subversion-perl and subversion-python and > swig (which I only maintained since the other two depend on it). I > anyone's interested, feel free to pick them up. "If anyone's...", of course. jw -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From lingalls at gmail.com Tue Sep 7 12:27:23 2004 From: lingalls at gmail.com (Logan Ingalls) Date: Tue, 7 Sep 2004 08:27:23 -0400 Subject: [clc-devel] Gmail Message-ID: <26616bd9040907052715372858@mail.gmail.com> (This is off-topic, but since this list includes all of the people I wanted to be sure to include, I'm sending it anyhow. Feel free to chew me out if this is inappropriate abuse of clc-devel.) I have six gmail invitations. All of the maintainers put forth such a huge amount of effort that I appreciate (literally) on a daily basis, so I'm offering them to you guys. First come, first served. Logan From jw at tks6.net Fri Sep 10 11:04:37 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Fri, 10 Sep 2004 13:04:37 +0200 Subject: [clc-devel] unmaintained; next try Message-ID: <20040910110437.GA4402@hoc> Hi there, As you might know many packages in unmaintained are outdated or even non-functional. Some of them have never versions in httpup repositories. We keep getting bug reports against those unmaintained ports, which means that some of us have to look after those ports (or defer the bug reports). I've been discussing with Juergen what the goal of CLC is; the choices were: 1. Have ports which we actively maintain 2. Have ports which seem important for a linux distribution The initial goal of CLC was to do the first of the two; as a consequence of this, we should not serve ports we don't maintain actively. Some time ago, having a collection like clc/unstable or unmaintained made sense since there was no alternative way to share ports. This is not the case anymore, and we could go back to follow goal #1 again. There is a certain need for ports which are "not quite ready" for contrib but are maintained by us. I'd therefore propose to drop unmaintained and start a new collection called 'testing'; ports which require further testing (both when the port or the ported software isn't stable) go there, but it should be our goal to move it to contrib or remove it altogether. 'testing' shouldn't be consider a permanent place for ports. Either they're fine for CLC, or they're not. Note that this would mean that we wouldn't have GNOME in our tree anymore, since rrm3 isn't around. IMO this would be the right consequence when a maintainer leaves, and we shouldn't try to keep the ports around but to find a new maintainer for them. Riders of Rohan, eerm, maintainers from CLC, Please discuss, comment or at least state whether you are in favor or against this step. Best regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From jw at tks6.net Fri Sep 10 11:10:32 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Fri, 10 Sep 2004 13:10:32 +0200 Subject: [clc-devel] unmaintained; next try In-Reply-To: <20040910110437.GA4402@hoc> References: <20040910110437.GA4402@hoc> Message-ID: <20040910111032.GB4402@hoc> Hi, On Fri, Sep 10, 2004 at 13:04:37 +0200, Johannes Winkelmann wrote: [...] > Note that this would mean that we wouldn't have GNOME in our tree > anymore, since rrm3 isn't around. IMO this would be the right > consequence when a maintainer leaves, and we shouldn't try to keep the > ports around but to find a new maintainer for them. Clarification: The wording was a bit unfortunate; what I mean is: We should try to keep the ports around without having someone looking after them. If they are important, we should either find someone to look after them or do it ourselfs (become the maintainer for them); otherwise, we should drop them. > Best regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From jw at tks6.net Fri Sep 10 11:16:23 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Fri, 10 Sep 2004 13:16:23 +0200 Subject: [clc-devel] unmaintained; next try In-Reply-To: <20040910111032.GB4402@hoc> References: <20040910110437.GA4402@hoc> <20040910111032.GB4402@hoc> Message-ID: <20040910111623.GC4402@hoc> Oh well, On Fri, Sep 10, 2004 at 13:10:32 +0200, Johannes Winkelmann wrote: > Hi, > > On Fri, Sep 10, 2004 at 13:04:37 +0200, Johannes Winkelmann wrote: > [...] > > Note that this would mean that we wouldn't have GNOME in our tree > > anymore, since rrm3 isn't around. IMO this would be the right > > consequence when a maintainer leaves, and we shouldn't try to keep the > > ports around but to find a new maintainer for them. > Clarification: The wording was a bit unfortunate; what I mean is: > We should try to keep the ports around without having someone looking > after them. "We shouldn't..." I'll double check my next correction mail, promised ;-) Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From sip at varlock.com Fri Sep 10 12:10:33 2004 From: sip at varlock.com (Simone Rota) Date: Fri, 10 Sep 2004 14:10:33 +0200 Subject: [clc-devel] unmaintained; next try In-Reply-To: <20040910110437.GA4402@hoc> References: <20040910110437.GA4402@hoc> Message-ID: <414199B9.6060006@varlock.com> On 09/10/04 13:04 Johannes Winkelmann wrote: > Hi there, Hi, > There is a certain need for ports which are "not quite ready" for > contrib but are maintained by us. I'd therefore propose to drop > unmaintained and start a new collection called 'testing'; ports which > require further testing (both when the port or the ported software isn't > stable) go there, but it should be our goal to move it to contrib or > remove it altogether. 'testing' shouldn't be consider a permanent place > for ports. Either they're fine for CLC, or they're not. Fine for me; it would be nice to have a collection slightly more....maintained than unmaintained. As you suggested I think that the 'testing' collection should be considered a temp thing, maybe without strict rules but with an approx. implicitly accepted expiration time (1 month?). > Note that this would mean that we wouldn't have GNOME in our tree > anymore, since rrm3 isn't around. IMO this would be the right > consequence when a maintainer leaves, and we shouldn't try to keep the > ports around but to find a new maintainer for them. > > Riders of Rohan, eerm, maintainers from CLC, Please discuss, comment or > at least state whether you are in favor or against this step. I support the proposal. So far I think we've got a quite solid port repository for CRUX (base + opt + contrib); solving the problems of ports nobody maintains and ports not ready for prime time would certainly improve the quality of the CLC offer (that sounds like marketing blurbs). From the other side I see a little more work for maintainers (it is possible that most used unmaintained ports will end up in contrib), but it's OK for me. Regards, Simone. -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From danm at gmx.li Fri Sep 10 15:42:21 2004 From: danm at gmx.li (Daniel Mueller) Date: Fri, 10 Sep 2004 17:42:21 +0200 Subject: [clc-devel] unmaintained; next try In-Reply-To: <20040910110437.GA4402@hoc> References: <20040910110437.GA4402@hoc> Message-ID: <20040910174221.05bbee28@torax.danm.de> On Fri, 10 Sep 2004 13:04:37 +0200 Johannes Winkelmann wrote: > [..] > ports. This is not the case anymore, and we could go back to follow > goal #1 again. > [..] Drop unmaintained :-) I'd be happy to get rid of it. The testing tree is a good idea. bye, danm -- Daniel Mueller Berlin, Germany (OpenPGP: 1024D/126EC290) From jue at jue.li Sun Sep 12 11:12:18 2004 From: jue at jue.li (Juergen Daubert) Date: Sun, 12 Sep 2004 13:12:18 +0200 Subject: [clc-devel] unmaintained; next try In-Reply-To: <20040910110437.GA4402@hoc> References: <20040910110437.GA4402@hoc> Message-ID: <20040912111217.GA1195@jue.netz> Hi CLC maintainers, On Fri, Sep 10, 2004 at 01:04:37PM +0200, Johannes Winkelmann wrote: [...] > I'd therefore propose to drop unmaintained and start a new collection > called 'testing'; Yep, I think that's the way to go. > Note that this would mean that we wouldn't have GNOME in our tree > anymore, since rrm3 isn't around. IMO this would be the right > consequence when a maintainer leaves, and we shouldn't try to keep the > ports around but to find a new maintainer for them. Yes, it is. But we shouldn't delete all unmaintained ports from cvs, but simply remove the UNMAINTAINED tag, so it's easy for CLC maintainer to adopt ports again. At all, this will be a remarkable change in the CLC structure, so more comments from other maintainers are desirable. And, please, look again through the unmaintained collection, maybe one or another port will find its way to contrib. thanks in advance and kind regards J?rgen -- Juergen Daubert | mailto:jue at jue.li Korb, Germany | http://jue.li/crux From jw at tks6.net Sun Sep 12 12:22:35 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Sun, 12 Sep 2004 14:22:35 +0200 Subject: [clc-devel] unmaintained; next try In-Reply-To: <20040912111217.GA1195@jue.netz> References: <20040910110437.GA4402@hoc> <20040912111217.GA1195@jue.netz> Message-ID: <20040912122235.GA30097@hoc> Hi, On Sun, Sep 12, 2004 at 13:12:18 +0200, Juergen Daubert wrote: > Hi CLC maintainers, > > On Fri, Sep 10, 2004 at 01:04:37PM +0200, Johannes Winkelmann wrote: > > [...] [...] > Yes, it is. But we shouldn't delete all unmaintained ports from cvs, > but simply remove the UNMAINTAINED tag, so it's easy for CLC maintainer > to adopt ports again. Yeah, definitely. I think we should even write a short wiki page describing how to get them so interested packagers can start quickly; this would probable mean to just provide a clc-complete.cvsup file. > At all, this will be a remarkable change in the CLC structure, so more > comments from other maintainers are desirable. agreed > And, please, look again through the unmaintained collection, maybe one > or another port will find its way to contrib. While we should do this from time to time anyway, we should have an extra close look at the ports from unmaintained once we decide to remove the tag; collect a list of ports to be dropped in the wiki and have people go through it, removing those they want to maintain. Kind regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From tilman at code-monkey.de Mon Sep 13 17:27:28 2004 From: tilman at code-monkey.de (Tilman Sauerbeck) Date: Mon, 13 Sep 2004 19:27:28 +0200 Subject: [clc-devel] unmaintained; next try In-Reply-To: <20040910110437.GA4402@hoc> References: <20040910110437.GA4402@hoc> Message-ID: <20040913172728.GA24732@code-monkey.de> Johannes Winkelmann [2004-09-10 16:24]: > contrib but are maintained by us. I'd therefore propose to drop > unmaintained and start a new collection called 'testing'; ports which > require further testing (both when the port or the ported software isn't > stable) go there, but it should be our goal to move it to contrib or > remove it altogether. 'testing' shouldn't be consider a permanent place > for ports. Either they're fine for CLC, or they're not. I like the idea. I'll look through unmaintained now and see whether there are any ports that I could maintain, there are quite a few in there that would be sad to loose. -- Regards, Tilman From per at fukt.bth.se Mon Sep 13 21:18:52 2004 From: per at fukt.bth.se (Per Liden) Date: Mon, 13 Sep 2004 23:18:52 +0200 (CEST) Subject: [clc-devel] unmaintained; next try In-Reply-To: <20040910174221.05bbee28@torax.danm.de> Message-ID: On Fri, 10 Sep 2004, Daniel Mueller wrote: > On Fri, 10 Sep 2004 13:04:37 +0200 > Johannes Winkelmann wrote: > > > [..] > > ports. This is not the case anymore, and we could go back to follow > > goal #1 again. > > [..] > > Drop unmaintained :-) > > I'd be happy to get rid of it. The testing tree is a good idea. I second that. /Per From guerrilla_thought at gmx.de Mon Sep 13 23:02:11 2004 From: guerrilla_thought at gmx.de (Anthony de Almeida Lopes) Date: Tue, 14 Sep 2004 01:02:11 +0200 (MEST) Subject: [clc-devel] unmaintained; next try References: Message-ID: <21753.1095116531@www6.gmx.net> will there still be a way to get ahold of those ports? i use a couple of them. i suppose i'll maintain them in my own repository if it comes to that. have a good one, tony -- * * * Anthony de Almeida Lopes guerrilla_thought at gmx.de AIM: whatsheon * * * "And someone else might feel something scratching in his mouth. he goes to the mirror opens his mouth: and his tongue is an enormous, live centipede, rubbing its legs together and scraping his palate. He'd like to spit it out, but the centipede is part of him and he will to tear it out with his own hands..." -- Jean Paul Sartre * * * Superg?nstige DSL-Tarife + WLAN-Router f?r 0,- EUR* Jetzt zu GMX wechseln und sparen http://www.gmx.net/de/go/dsl From jw at tks6.net Wed Sep 15 12:54:53 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Wed, 15 Sep 2004 14:54:53 +0200 Subject: [clc-devel] Docs in Wiki Message-ID: <20040915125453.GA26128@hoc> Hi, I was wondering whether we should call for contributors to write some documentation in our Wiki; howtos, configuration tips, screenshots etc. Anyone in favour of that? Kind regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From jaeger at morpheus.net Wed Sep 15 15:35:59 2004 From: jaeger at morpheus.net (Matt Housh) Date: Wed, 15 Sep 2004 10:35:59 -0500 Subject: [clc-devel] Docs in Wiki In-Reply-To: <20040915125453.GA26128@hoc> References: <20040915125453.GA26128@hoc> Message-ID: <4148615F.2090700@morpheus.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Johannes Winkelmann wrote: | Hi, | | I was wondering whether we should call for contributors to write some | documentation in our Wiki; howtos, configuration tips, screenshots etc. | Anyone in favour of that? | | Kind regards, Johannes I don't see any reason not to; as Jay said on the crux list, I'm sure we've all got something to contribute. Matt (jaeger at freenode/#crux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBSGFfGFVQ7mavvGgRAp/KAKCBJrk1m8Al3goXE2cRLZKXYK0cIACcCxI/ vinDR/w1t9g2xuCOXQZcCYc= =qJf2 -----END PGP SIGNATURE----- From jw at tks6.net Wed Sep 15 18:02:33 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Wed, 15 Sep 2004 20:02:33 +0200 Subject: [clc-devel] opera, anyone? (port to adopt) Message-ID: <20040915180233.GA4439@hoc> Hey, I'm currently maintaining contrib/opera but stopped using it a good while ago. I think it's a good browser and worth having in contrib, but I think it would be better if we had a maintainer who is actually using it, so if someone's interested in maintaining opera, please let me know. Otherwise, I'll continue to maintain it, of course. Regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From jw at tks6.net Thu Sep 16 06:08:05 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Thu, 16 Sep 2004 08:08:05 +0200 Subject: [clc-devel] RFC: wrapper for ccache and distcc In-Reply-To: <20040901132334.GC32065@hoc> References: <20040901132334.GC32065@hoc> Message-ID: <20040916060805.GB4439@hoc> Hi, On Wed, Sep 01, 2004 at 15:23:34 +0200, Johannes Winkelmann wrote: > Hi, > > A work collegue of mine brought to my attention that building tcl fails > when using ccache, and I realized that the error is quite simple (not to > say stupid ;-)); ccache comes with wrappers for gcc and g++ which just > call 'ccache gcc $*' or 'ccache g++ $*'. Unfortunately this creates a > problem when the Makefile calls the wrapper like this: > ccache-gcc [...] -DTCL_WIDE_INT_TYPE=long\ long > > Since the wrapper is a shell script and will call > ccache gcc $* > This will break the last argument into two ("-DTCL_WIDE_INT_TYPE=long" > and "long"). Maybe there's a way to work around that, but I wouldn't > know about it. > This e.g. breaks tcl, and I remember it also broke gimp < 2 (not sure > about >= 2). > > Anyway, if ccache (the application) is called as gcc (by renaming it or > creating a symlink called 'gcc'), it works fine. The additional > advantage of this is that even if a Makefile doesn't use the CC and CXX > variables, this will work. > The problem (and reason why I didn't do it like this earlier) is that > those symlinks must be put somewhere, and I'm not sure what the right > place is; IMO it should be something which isn't in the path usually, > which means that /bin shouldn't even be considered. > > gentoo uses /usr/lib/bin/{gcc,cc,g++,c++}, not sure what others use. Are > there any suggestions what might be a good path for CRUX? I'd like to ask for a few more comments on this question, since the symlink variant has still a higher success rate compared to the wrapper solution. /usr/share/gcc-wrappers/{distcc,ccache}/{gcc,g++} /usr/lib/gcc-wrappers/{distcc,ccache} ? Regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From vector at pp.nic.fi Thu Sep 16 06:15:25 2004 From: vector at pp.nic.fi (Jukka Heino) Date: Thu, 16 Sep 2004 09:15:25 +0300 (EEST) Subject: [clc-devel] opera, anyone? (port to adopt) Message-ID: <6637946.1095315325180.JavaMail.vector@pp.nic.fi> > Hey, > > I'm currently maintaining contrib/opera but stopped using it a good > while ago. I think it's a good browser and worth having in contrib, but > I think it would be better if we had a maintainer who is actually using > it, so if someone's interested in maintaining opera, please let me know. > Otherwise, I'll continue to maintain it, of course. I'm using Opera on some low-end computers, so if you don't want to maintain anymore, I could very well take care of it. // Jukka From vector at pp.nic.fi Thu Sep 16 06:21:38 2004 From: vector at pp.nic.fi (Jukka Heino) Date: Thu, 16 Sep 2004 09:21:38 +0300 (EEST) Subject: [clc-devel] RFC: wrapper for ccache and distcc Message-ID: <21808207.1095315698611.JavaMail.vector@pp.nic.fi> > I'd like to ask for a few more comments on this question, since the > symlink variant has still a higher success rate compared to the wrapper > solution. > > /usr/share/gcc-wrappers/{distcc,ccache}/{gcc,g++} > /usr/lib/gcc-wrappers/{distcc,ccache} > ? I've been using a symlink in ~/bin, but I agree, a system-wide solution would be better. I propose /usr/lib/{distcc,ccache}/bin since this would have the same structure as already existing ports (j2re, ant, db3...) Additionally it seems a bit more FHS-like than gcc-wrappers. // Jukka From jw at tks6.net Fri Sep 17 08:21:03 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Fri, 17 Sep 2004 10:21:03 +0200 Subject: [clc-devel] opera, anyone? (port to adopt) In-Reply-To: <6637946.1095315325180.JavaMail.vector@pp.nic.fi> References: <6637946.1095315325180.JavaMail.vector@pp.nic.fi> Message-ID: <20040917082103.GA17434@hoc> Hi, On Thu, Sep 16, 2004 at 09:15:25 +0300, Jukka Heino wrote: > >Hey, > > > >I'm currently maintaining contrib/opera but stopped using it a good > >while ago. I think it's a good browser and worth having in contrib, but > >I think it would be better if we had a maintainer who is actually using > >it, so if someone's interested in maintaining opera, please let me know. > >Otherwise, I'll continue to maintain it, of course. > > I'm using Opera on some low-end computers, so if you don't want to > maintain anymore, I could very well take care of it. Please do so, that would be great! Kind regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From jue at jue.li Fri Sep 17 13:48:47 2004 From: jue at jue.li (Juergen Daubert) Date: Fri, 17 Sep 2004 15:48:47 +0200 Subject: [clc-devel] Docs in Wiki In-Reply-To: <20040915125453.GA26128@hoc> References: <20040915125453.GA26128@hoc> Message-ID: <20040917134847.GA587@jue.netz> On Wed, Sep 15, 2004 at 02:54:53PM +0200, Johannes Winkelmann wrote: > Hi, > > I was wondering whether we should call for contributors to write some > documentation in our Wiki; howtos, configuration tips, screenshots etc. > Anyone in favour of that? Yep, I like the idea. From per at fukt.bth.se Sun Sep 19 21:37:38 2004 From: per at fukt.bth.se (Per Liden) Date: Sun, 19 Sep 2004 23:37:38 +0200 (CEST) Subject: [clc-devel] RFC: wrapper for ccache and distcc In-Reply-To: <21808207.1095315698611.JavaMail.vector@pp.nic.fi> Message-ID: On Thu, 16 Sep 2004, Jukka Heino wrote: > > I'd like to ask for a few more comments on this question, since the > > symlink variant has still a higher success rate compared to the wrapper > > solution. > > > > /usr/share/gcc-wrappers/{distcc,ccache}/{gcc,g++} > > /usr/lib/gcc-wrappers/{distcc,ccache} > > ? > > I've been using a symlink in ~/bin, but I agree, a system-wide solution > would be better. I propose /usr/lib/{distcc,ccache}/bin since this would > have the same structure as already existing ports (j2re, ant, db3...) > Additionally it seems a bit more FHS-like than gcc-wrappers. I agree, /usr/lib/{distcc,ccache}/ feels more like the CRUX way. /Per From ncrfgs at tin.it Sun Sep 19 22:36:38 2004 From: ncrfgs at tin.it (ncrfgs) Date: Mon, 20 Sep 2004 00:36:38 +0200 Subject: [clc-devel] RFC: Cross-compiling toolchain default location Message-ID: <20040919223638.GA831@ncrfgs3.ncrfgs> Hi, After having successfully built a cross-compiling toolchain thanks to cross-lfs (http://www.linuxfromscratch.org/~ryan/scripts/cross-lfs/), I'm trying to adapt the wonderful scripts written by Ryan Oliver for the Linux From Scratch system, to the form of some Pkgbuild package building scripts. Unfortunately while trying to accomplish this task I'm facing some problems, first of all the choice of the cross-compiling toolchain default location. What do you think is the best location in the filesystem for the cross-compiling toolchain or, in other words, what do you think is the best configure time prefix to use? At the moment I put it into /opt/ppc/usr but I wonder whether is there a way to make it to coexist with the "regular" toolchain in /usr or whether is there a better location to put it into. Another problem I'm facing from the package management point of view are the files that gcc and glibc share among the different build steps. Maybe it's a bit Off Topic but I hope some of you have some experiences to share. Let's take for example the case of gcc. The gcc-static package shares all of its files with the gcc-shared package while the following files are included in the gcc-shared package only. $PREFIX/lib/gcc-lib/powerpc-unknown-linux-gnu/3.3.3-hammer/libgcc_eh.a $PREFIX/powerpc-unknown-linux-gnu/ $PREFIX/powerpc-unknown-linux-gnu/lib/ $PREFIX/powerpc-unknown-linux-gnu/lib/libgcc_s.so -> libgcc_s.so.1 $PREFIX/powerpc-unknown-linux-gnu/lib/libgcc_s.so.1 Should gcc-shared be seen as a gcc-static "upgrade"? Or may I safely delete from the gcc-shared package all the files already installed by gcc-static and leave only the new ones (namely libgcc_eh.a and libgcc_s.so*)? What when, just like in the case of the different glibc builds, the two packages shares only some files? Thanks in advance. Best regards. -- Value your freedom, or you will lose it, teaches history. ``Don't bother us with politics,'' respond those who don't want to learn. -- Richard M. Stallman http://www.gnu.org/philosophy/linux-gnu-freedom.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From vector at pp.nic.fi Tue Sep 21 11:49:57 2004 From: vector at pp.nic.fi (Jukka Heino) Date: Tue, 21 Sep 2004 14:49:57 +0300 (EEST) Subject: [clc-devel] Software licenses Message-ID: <18476922.1095767397557.JavaMail.vector@pp.nic.fi> Hi, Now that Simone Rota has committed his datastudio port into contrib, I began to wonder if CLC has some sort of policy on what software licenses should be allowed in contrib. At least one user was concerned that he might accidentally install software which would require a commercial license for the purpose he's using it for. I, for one, would find something like a "License" field in Pkgfiles useful so that with a quick glance one could see under which terms the software is released (GPL, BSD...). What do others think? Regards, // Jukka From ncrfgs at tin.it Tue Sep 21 12:53:34 2004 From: ncrfgs at tin.it (ncrfgs) Date: Tue, 21 Sep 2004 14:53:34 +0200 Subject: [clc-devel] Software licenses In-Reply-To: <18476922.1095767397557.JavaMail.vector@pp.nic.fi> References: <18476922.1095767397557.JavaMail.vector@pp.nic.fi> Message-ID: <20040921125334.GA27503@ncrfgs3.ncrfgs> On Tue, Sep 21, 2004 at 02:49:57PM +0300, Jukka Heino wrote: > Now that Simone Rota has committed his datastudio port into contrib, I > began to wonder if CLC has some sort of policy on what software licenses > should be allowed in contrib. At least one user was concerned that he > might accidentally install software which would require a commercial > license for the purpose he's using it for. I, for one, would find > something like a "License" field in Pkgfiles useful so that with a quick > glance one could see under which terms the software is released (GPL, > BSD...). What do others think? I agree. It would be nice (at least for me) to know what kind of licence the software I'm going to install is released under in a fast way. But I'm not sure a tag is the best way to accomplish this task. Maybe a note in a README file or a LICENSE file on its own, just when the License isn't OSI approved, would suit best this need. I think the Pkgfile should try to contain only informations related to the package building, that's why I don't believe in a tag bases solution to this problem. This is just the opinion of a user, though, because unfortunately I'm not a CLC developer... -_- Best regards. -- Value your freedom, or you will lose it, teaches history. ``Don't bother us with politics,'' respond those who don't want to learn. -- Richard M. Stallman http://www.gnu.org/philosophy/linux-gnu-freedom.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From riemer at ppprs1.phy.tu-dresden.de Tue Sep 21 13:01:10 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Tue, 21 Sep 2004 15:01:10 +0200 Subject: [clc-devel] Software licenses In-Reply-To: <18476922.1095767397557.JavaMail.vector@pp.nic.fi> References: <18476922.1095767397557.JavaMail.vector@pp.nic.fi> Message-ID: <1095771670.41502616d9115@mail.iapp.de> Hello, Zitat von Jukka Heino : > license for the purpose he's using it for. I, for one, would find > something like a "License" field in Pkgfiles useful so that with a > quick > glance one could see under which terms the software is released > (GPL, > BSD...). What do others think? Please, no useless limitation to "free" software. Not in contrib (maybe/surely in base, opt). I want to use the system, not pray in the church of "free" world. I think, a "License" field in Pkgfile is a good idea. So everybody can see if he has to respect some license restriction. And I don't expect that someone will put hacked commercial software on a server and so on... Best regards, Tilo -- Tilo Riemer mailto:riemer at lincvs.org Dresden, Germany http://www.lincvs.org http://www.iapp.de/~riemer/projects From jw at tks6.net Tue Sep 21 13:24:03 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Tue, 21 Sep 2004 15:24:03 +0200 Subject: [clc-devel] Software licenses In-Reply-To: <18476922.1095767397557.JavaMail.vector@pp.nic.fi> References: <18476922.1095767397557.JavaMail.vector@pp.nic.fi> Message-ID: <41502B73.8060406@tks6.net> Jukka Heino wrote: > Hi, > > Now that Simone Rota has committed his datastudio port into contrib, I > began to wonder if CLC has some sort of policy on what software licenses > should be allowed in contrib. At least one user was concerned that he > might accidentally install software which would require a commercial > license for the purpose he's using it for. I, for one, would find > something like a "License" field in Pkgfiles useful so that with a quick > glance one could see under which terms the software is released (GPL, > BSD...). What do others think? I'm a bit torn since on one hand, I think users should just be able to install the software from our ports tree without caring about legal issues; on the other hand, this would basically mean that we wouldn't allow any commercial packages in the ports tree. Regarding DataStudio, if you start it you have to explicitely select whether you want to use it for personal use only: http://jw.tks6.net/files/crux/ds.png This is very similar to what we do in Qt, where we assume that users want the GPL'ed version (where commercial licenses could be selected as well), and I don't think this is a problem as you can legally have a copy on your harddisk which is not used (as a personal edition), and you have to idendify the mode of usage before actually being able to use it. Beyond that, I'd rather not provide ports which require a commercial license for non-personal use if there's no such dialog at startup, than introducing a 'license' field in Pkgfiles. In such cases, I'd rather omit the download and have people fetch the input files themselves, since I think it would be too easy to just overlook the license field. Whether the license header adds enough value independently from the commercial license discussion... I'm not so sure. IMO for that to be nice, we should give the user access to the license itself, which would imply that the user has it installed (optionally, of course). I don't think something like "apache license, version 2" is enough to write in a package, since people will still have to look it up (just like looking up the license in the first place). We could compile a set of licenses, identify them using keys (e.g. GPL, LGPL, APL2.0 etc.) and put them into /usr/share/licenses/$KEY; but then, I'm not sure if this is worth the effort, though. Kind regards, Johannes -- "no sig today" -- jw From sip at varlock.com Tue Sep 21 13:41:23 2004 From: sip at varlock.com (Simone Rota) Date: Tue, 21 Sep 2004 15:41:23 +0200 Subject: [clc-devel] Software licenses In-Reply-To: <18476922.1095767397557.JavaMail.vector@pp.nic.fi> References: <18476922.1095767397557.JavaMail.vector@pp.nic.fi> Message-ID: <41502F83.4000707@varlock.com> On 09/21/04 13:49 Jukka Heino wrote: > Hi, > > Now that Simone Rota has committed his datastudio port into contrib, I > began to wonder if CLC has some sort of policy on what software licenses > should be allowed in contrib. At least one user was concerned that he > might accidentally install software which would require a commercial > license for the purpose he's using it for. I, for one, would find > something like a "License" field in Pkgfiles useful so that with a quick > glance one could see under which terms the software is released (GPL, > BSD...). What do others think? Hi, in the case of datastudio, license information and selection is displayed at first run, so a misunderstanding is not possible. (just saw Johannes pointed out this as well) Assuming the problem is not limited to that port, I'm more in favour of a specific solution (as suggested by ncrfgs); the README file seems an appropriate place for me. This way we won't have to add overhead to other ports. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From ncrfgs at tin.it Tue Sep 21 22:59:56 2004 From: ncrfgs at tin.it (ncrfgs) Date: Wed, 22 Sep 2004 00:59:56 +0200 Subject: [clc-devel] Re: important changes in contrib/ccache and contrib/distcc In-Reply-To: <20040921220447.GB3631@hoc> References: <20040921213103.GA3631@hoc> <20040921215402.GA8005@ncrfgs3.ncrfgs> <20040921220447.GB3631@hoc> Message-ID: <20040921225956.GA18574@ncrfgs3.ncrfgs> On Wed, Sep 22, 2004 at 12:04:47AM +0200, Johannes Winkelmann wrote: > > > This means that you no longer have to export CC and CXX, but prepend the > > > respective path to your $PATH variable: for ccache, prepend > > > /usr/lib/ccache to your path; for distcc, /usr/lib/distcc. > > > > > > Please let me know if there are any problems. > > > > What if one uses both at the same time? > > There's a section on the in the man page of distcc; basically, what you > do is just prepending both paths to the PATH variable, like: > PATH=/usr/lib/ccache:/usr/lib/distcc:$PATH Yes sorry. I didn't explain myself well. I meant what if one uses both at the same time, how can you make it to work with the "export PATH" way? I didn't think PATH=/usr/lib/ccache:/usr/lib/distcc:$PATH would have worked, but then I read the distcc man page masquerade section and now I understand. It can work because distcc intercepts the calls to the compiler and then removes itself from the PATH to find the real compiler. I think ccache behaves the same. Thanks for the pointer. Best regards. -- Value your freedom, or you will lose it, teaches history. ``Don't bother us with politics,'' respond those who don't want to learn. -- Richard M. Stallman http://www.gnu.org/philosophy/linux-gnu-freedom.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ncrfgs at tin.it Tue Sep 21 23:06:11 2004 From: ncrfgs at tin.it (ncrfgs) Date: Wed, 22 Sep 2004 01:06:11 +0200 Subject: [clc-devel] Re: important changes in contrib/ccache and contrib/distcc In-Reply-To: <20040921225956.GA18574@ncrfgs3.ncrfgs> References: <20040921213103.GA3631@hoc> <20040921215402.GA8005@ncrfgs3.ncrfgs> <20040921220447.GB3631@hoc> <20040921225956.GA18574@ncrfgs3.ncrfgs> Message-ID: <20040921230611.GA18653@ncrfgs3.ncrfgs> Sorry I sent it to the wrong ML. Best regards. -- Value your freedom, or you will lose it, teaches history. ``Don't bother us with politics,'' respond those who don't want to learn. -- Richard M. Stallman http://www.gnu.org/philosophy/linux-gnu-freedom.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From lingalls at gmail.com Tue Sep 21 23:40:20 2004 From: lingalls at gmail.com (Logan Ingalls) Date: Tue, 21 Sep 2004 19:40:20 -0400 Subject: [clc-devel] Re: Your CLC maintainership In-Reply-To: <20040921190448.GA984@code-monkey.de> References: <20040921190448.GA984@code-monkey.de> Message-ID: <26616bd90409211640551d7e47@mail.gmail.com> Hi all, I haven't really been keeping up with the ports that I'm maintaining. I've been extremely busy lately with work, and they cut off my access to the outside world (i.e. CVS). I only have a few ports in contrib, but I don't get the chance to update them that frequently. It would probably be best if I retired from official maintainership and someone else take electricsheep, graphviz, or snort (all of which are probably not up-to-date). I still use Crux and I still love it, but since I can't really contribute to ports very much with my work schedule and their draconian firewall rules, this would probably help CLC and contrib. I do have a couple of ports that I do keep up-to-date for work (vmware, for one). I'll probably make an httpup repo for those, since that's what httpup repos are for. (Thanks to Tilman for nudging me to make a decision on this.) -- Logan Ingalls http://plutor.org/ From jasonthomasdolan at yahoo.com Tue Sep 28 02:06:56 2004 From: jasonthomasdolan at yahoo.com (Jay Dolan) Date: Mon, 27 Sep 2004 19:06:56 -0700 (PDT) Subject: [clc-devel] Application for CLC Maintainer Message-ID: <20040928020656.70477.qmail@web41502.mail.yahoo.com> Hi guys :) Most of you know me from the general mailing list and from IRC. My name's Jay Dolan, and I'd like to become a maintainer. My ports have been online for several months, and are now located at http://jdolan.dyndns.org/jaydolan/ports. Of the ones found there, I think most of the non-gaming ports are decent candidates for contrib. The odd-balls and gaming ports should probably remain in my own repository. As far as a well-defined list of ports currently in unmaintained that I'd be willing to adopt - I'm not terribly sure. I'd like to take care of orphaned audio / multimedia apps as well as some Java-centric ones. But if there's a certain group that requires attention, I'll consider taking said ports on. GNOME does interest me, but Jaeger is already providing a nice collection in his repository. The other area I'd like to help in is with the web portal. I'm a decent technical writer, so populating / cleaning up the Wiki would be a lot of fun for me. In all, I'm pretty committed to CRUX, and I think my ideas generally coincide with the CLC. Thanks for your consideration, ===== Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com From sip at varlock.com Tue Sep 28 11:14:40 2004 From: sip at varlock.com (Simone Rota) Date: Tue, 28 Sep 2004 13:14:40 +0200 Subject: [clc-devel] Application for CLC Maintainer In-Reply-To: <20040928020656.70477.qmail@web41502.mail.yahoo.com> References: <20040928020656.70477.qmail@web41502.mail.yahoo.com> Message-ID: <415947A0.3020808@varlock.com> On 09/28/04 04:06 Jay Dolan wrote: > Hi guys :) > > Most of you know me from the general mailing list and > from IRC. My name's Jay Dolan, and I'd like to become > a maintainer. [cut] I support Jay's application; his ports seem clean, he's writing some interesting tool (pkgsync), plus doc writers / maintainers are always welcome. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From danm at gmx.li Tue Sep 28 17:03:26 2004 From: danm at gmx.li (Daniel Mueller) Date: Tue, 28 Sep 2004 19:03:26 +0200 Subject: [clc-devel] Application for CLC Maintainer In-Reply-To: <20040928020656.70477.qmail@web41502.mail.yahoo.com> References: <20040928020656.70477.qmail@web41502.mail.yahoo.com> Message-ID: <20040928190326.1b4fa92f@torax.danm.de> Hi, your ports are looking fine. Tech-writers are also highly welcome. I'd like to see you as a new CLC maintainer so you'll get my vote. bye, danm -- Daniel Mueller Berlin, Germany (OpenPGP: 1024D/126EC290) From jw at tks6.net Tue Sep 28 18:23:45 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Tue, 28 Sep 2004 20:23:45 +0200 Subject: [clc-devel] Application for CLC Maintainer In-Reply-To: <20040928020656.70477.qmail@web41502.mail.yahoo.com> References: <20040928020656.70477.qmail@web41502.mail.yahoo.com> Message-ID: <20040928182345.GA26839@hoc> Hi, On Mon, Sep 27, 2004 at 19:06:56 -0700, Jay Dolan wrote: > Hi guys :) > > Most of you know me from the general mailing list and > from IRC. My name's Jay Dolan, and I'd like to become > a maintainer. Not that you'd need any more support after Simone's and Daniel's mails, but both Jukka Heino and me support your application here. We might have a discussion about java related ports one day, and how we could organize them in a good way. Kind regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From jaeger at morpheus.net Tue Sep 28 18:24:07 2004 From: jaeger at morpheus.net (Matt Housh) Date: Tue, 28 Sep 2004 13:24:07 -0500 Subject: [clc-devel] Application for CLC Maintainer In-Reply-To: <20040928020656.70477.qmail@web41502.mail.yahoo.com> References: <20040928020656.70477.qmail@web41502.mail.yahoo.com> Message-ID: <4159AC47.4060000@morpheus.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jay gets my vote as well. Good ports and I'm happy to see people interested in wiki contribution/cleanup. :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBWaxHGFVQ7mavvGgRApVZAJ9pIQEFGqGx255cnEKWZLqJnminGgCeIpDf Iyz1n0ak3n+L9nztnqJqYXQ= =lMoT -----END PGP SIGNATURE----- From jaeger at morpheus.net Wed Sep 29 15:55:17 2004 From: jaeger at morpheus.net (Matt Housh) Date: Wed, 29 Sep 2004 10:55:17 -0500 Subject: [clc-devel] Application for CLC Maintainer In-Reply-To: <20040928020656.70477.qmail@web41502.mail.yahoo.com> References: <20040928020656.70477.qmail@web41502.mail.yahoo.com> Message-ID: <415ADAE5.7000405@morpheus.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jay's been added to the clc server and the wiki. Fear him. Matt (jaeger at freenode/#crux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBWtrlGFVQ7mavvGgRAsuLAJ0a7dioagQGNwkL1L5SOZCnJVotgwCbBnMu eFBNdeS+vrbkkrRm5covhLI= =yRHR -----END PGP SIGNATURE----- From jasonthomasdolan at yahoo.com Thu Sep 30 00:13:09 2004 From: jasonthomasdolan at yahoo.com (Jay Dolan) Date: Wed, 29 Sep 2004 17:13:09 -0700 (PDT) Subject: [clc-devel] Application for CLC Maintainer In-Reply-To: <415ADAE5.7000405@morpheus.net> Message-ID: <20040930001309.87353.qmail@web41506.mail.yahoo.com> --- Matt Housh wrote: > Jay's been added to the clc server and the wiki. > Fear him. > > Matt (jaeger at freenode/#crux) Muhahaha! Thanks for your votes of confidence :) I look forward to working with and learning from you all. ===== Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com