From Juergen.Daubert at t-online.de Sun Feb 1 11:27:14 2004 From: Juergen.Daubert at t-online.de (Juergen Daubert) Date: Sun, 1 Feb 2004 12:27:14 +0100 Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link In-Reply-To: <401BF101.6090007@varlock.com> References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc> <401BF101.6090007@varlock.com> Message-ID: <20040201112714.GA20342@jue.netz> On Sat, Jan 31, 2004 at 07:16:33PM +0100, Simone Rota wrote: > 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. I'd included the blackdown j2re because the sun's mozilla plugin doesn't work with CRUX. But nowadays this is deprecated. Most comprehensive would be to have only one java port, in this case the j2sdk of course. > >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? Yes, I agree, but are not able to do this comparison, hopefully we have some java guru in our team ;) Greetings J?rgen -- juergen.daubert at t-online.de From Juergen.Daubert at t-online.de Sun Feb 1 11:27:14 2004 From: Juergen.Daubert at t-online.de (Juergen Daubert) Date: Sun, 1 Feb 2004 12:27:14 +0100 Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link In-Reply-To: <401BF101.6090007@varlock.com> References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc> <401BF101.6090007@varlock.com> Message-ID: <20040201112714.GA20342@jue.netz> On Sat, Jan 31, 2004 at 07:16:33PM +0100, Simone Rota wrote: > 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. I'd included the blackdown j2re because the sun's mozilla plugin doesn't work with CRUX. But nowadays this is deprecated. Most comprehensive would be to have only one java port, in this case the j2sdk of course. > >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? Yes, I agree, but are not able to do this comparison, hopefully we have some java guru in our team ;) Greetings J?rgen -- juergen.daubert at t-online.de From sip at varlock.com Sun Feb 1 14:03:40 2004 From: sip at varlock.com (Simone Rota) Date: Sun, 01 Feb 2004 15:03:40 +0100 Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link In-Reply-To: <20040201112714.GA20342@jue.netz> References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc> <401BF101.6090007@varlock.com> <20040201112714.GA20342@jue.netz> Message-ID: <401D073C.8060407@varlock.com> On 02/01/04 12:27 Juergen Daubert wrote: > I'd included the blackdown j2re because the sun's mozilla plugin doesn't > work with CRUX. But nowadays this is deprecated. Most comprehensive > would be to have only one java port, in this case the j2sdk of course. I personally won't mind having only the j2skd port since I'd use it anyway. Yet it could be considered a not-so-small overhead for people only wanting the plugin or the vm, expecially for the ones with a slow connection, since the size difference is notable. Just a consideration, I'm quite neutral on this topic. -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From riemer at ppprs1.phy.tu-dresden.de Mon Feb 2 08:33:05 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Mon, 2 Feb 2004 09:33:05 +0100 Subject: [clc-devel] new port of LinCVS Message-ID: <20040202083305.GA7185@ppprs1.phy.tu-dresden.de> Hello, a new port of current LinCVS 1.3.0 is available and attached. Best regards, Tilo -------------- next part -------------- A non-text attachment was scrubbed... Name: lincvs-1.3.0-0-CRUX-port.tgz Type: application/x-gtar Size: 1045 bytes Desc: not available URL: From riemer at ppprs1.phy.tu-dresden.de Mon Feb 2 08:36:42 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Mon, 2 Feb 2004 09:36:42 +0100 Subject: [clc-devel] ROX-ports Message-ID: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> Hello, I took a look inside of some ROX app ports. I think it's not the best idea to break the AppDir structure which is used by ROX apps. Instead of installing the binary to /usr/bin it should be better (and simple) to create a startscript which calls the binary installed in the AppDir like /usr/share/ROX/ROX-Pager. See also the newest LinCVS port. AppDir styled programs search for resources in the AppDir. They can't find it if the binary is installed outside of the AppDir. Best regards, Tilo From sip at varlock.com Mon Feb 2 12:26:58 2004 From: sip at varlock.com (Simone Rota) Date: Mon, 02 Feb 2004 13:26:58 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> Message-ID: <401E4212.7030309@varlock.com> On 02/02/04 09:36 Tilo Riemer wrote: > Hello, > > I took a look inside of some ROX app ports. > I think it's not the best idea to break the AppDir structure which is used > by ROX apps. > Instead of installing the binary to /usr/bin it should be better (and > simple) to create a startscript which calls the binary installed in the > AppDir like /usr/share/ROX/ROX-Pager. See also the newest LinCVS port. > > AppDir styled programs search for resources in the AppDir. They can't find > it if the binary is installed outside of the AppDir. Hi Tilo, I'm not sure I undersand you, I think the applets already install files in /usr/share/rox. Are you referring to the rox port itsel? I'll have a deeper look into the issue this evening, gotta go now. Thanks for reporting Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From tillbiedermann at yahoo.de Mon Feb 2 13:02:01 2004 From: tillbiedermann at yahoo.de (Till Biedermann) Date: Mon, 02 Feb 2004 14:02:01 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> Message-ID: <1075726920.2220.21.camel@Horst.wg.lan> On Mon, 2004-02-02 at 09:36, Tilo Riemer wrote: > Hello, > > I took a look inside of some ROX app ports. > I think it's not the best idea to break the AppDir structure which is used > by ROX apps. Hi, i agree. I suggest to have an 'official' AppDir in Crux for AppDir styles programs. The executables could have a link or a startscript in /usr/bin for programs that dont know how to handle AppDirs. btw: I use ROX as desktop since two weeks - it's the best desktop i ever tryed. VERY fast and VERY easy to use. Regards Till -- http://www.tbmnet.de From riemer at ppprs1.phy.tu-dresden.de Mon Feb 2 13:48:57 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Mon, 2 Feb 2004 14:48:57 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <401E4212.7030309@varlock.com> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <401E4212.7030309@varlock.com> Message-ID: <20040202134857.GB19867@ppprs1.phy.tu-dresden.de> Hello Simone, On Mon, Feb 02, 2004 at 01:26:58PM +0100, Simone Rota wrote: > I'm not sure I undersand you, I think the applets > already install files in /usr/share/rox. Are you referring to the > rox port itsel? Sorry, just the wrong example! But rox-filer is installed breaking the AppDir structure (I believe). Best regards, Tilo From riemer at ppprs1.phy.tu-dresden.de Mon Feb 2 13:50:39 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Mon, 2 Feb 2004 14:50:39 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <1075726920.2220.21.camel@Horst.wg.lan> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> Message-ID: <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> Hello, On Mon, Feb 02, 2004 at 02:02:01PM +0100, Till Biedermann wrote: > i agree. I suggest to have an 'official' AppDir in Crux for AppDir > styles programs. The executables could have a link or a startscript in > /usr/bin for programs that dont know how to handle AppDirs. accordingly to the available rox ports the appdir directory should be /usr/share/rox. > btw: I use ROX as desktop since two weeks - it's the best desktop i ever > tryed. VERY fast and VERY easy to use. full ack :-))) Best regards, Tilo From tillbiedermann at yahoo.de Mon Feb 2 17:19:08 2004 From: tillbiedermann at yahoo.de (Till Biedermann) Date: Mon, 02 Feb 2004 18:19:08 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> Message-ID: <1075742348.543.14.camel@Horst.wg.lan> Hi, On Mon, 2004-02-02 at 14:50, Tilo Riemer wrote: > accordingly to the available rox ports the appdir directory should be > /usr/share/rox. yes, but /usr/share/Apps or /usr/share/AppDir is a better solution in my opinion, because rox itself is an AppDir-application. Regards Till -- http://www.tbmnet.de From sip at varlock.com Mon Feb 2 18:20:52 2004 From: sip at varlock.com (Simone Rota) Date: Mon, 02 Feb 2004 19:20:52 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <1075742348.543.14.camel@Horst.wg.lan> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> <1075742348.543.14.camel@Horst.wg.lan> Message-ID: <401E9504.3020904@varlock.com> On 02/02/04 18:19 Till Biedermann wrote: > Hi, > > On Mon, 2004-02-02 at 14:50, Tilo Riemer wrote: > >>accordingly to the available rox ports the appdir directory should be >>/usr/share/rox. > > > yes, but /usr/share/Apps or /usr/share/AppDir is a better solution in my > opinion, because rox itself is an AppDir-application. > > Regards Till Hi Till, I'd prefer to use /usr/share/Apps too (and if needed /usr/share/Choices, etc.) That would go against CRUX/CLC package policies, but I think it's a necessary step since one of ROX main characteristics is the filesystem layout itself. If there are no objections I'll begin working on ROX ports tonight. (change fs layout, general cleaning and testing). I no longer use ROX-Session, but I'll try to move it to contrib, for completeness. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From sip at varlock.com Mon Feb 2 18:21:06 2004 From: sip at varlock.com (Simone Rota) Date: Mon, 02 Feb 2004 19:21:06 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <20040202134857.GB19867@ppprs1.phy.tu-dresden.de> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <401E4212.7030309@varlock.com> <20040202134857.GB19867@ppprs1.phy.tu-dresden.de> Message-ID: <401E9512.5080200@varlock.com> On 02/02/04 14:48 Tilo Riemer wrote: > Hello Simone, Hi Tilo, > Sorry, just the wrong example! > But rox-filer is installed breaking the AppDir structure (I believe). > > > Best regards, Tilo Now I see. I agree it would be better to respect Rox policy instead of the CRUX in this case. See my reply to Till in this thread for further considerations. -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From riemer at ppprs1.phy.tu-dresden.de Mon Feb 2 20:47:01 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Mon, 2 Feb 2004 21:47:01 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <1075742348.543.14.camel@Horst.wg.lan> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> <1075742348.543.14.camel@Horst.wg.lan> Message-ID: <20040202204701.GA6675@ppprs1.phy.tu-dresden.de> Hello, On Mon, Feb 02, 2004 at 06:19:08PM +0100, Till Biedermann wrote: > On Mon, 2004-02-02 at 14:50, Tilo Riemer wrote: > > accordingly to the available rox ports the appdir directory should be > > /usr/share/rox. > > yes, but /usr/share/Apps or /usr/share/AppDir is a better solution in my > opinion, because rox itself is an AppDir-application. /usr/share/rox contains AppDirs like ROX-Filer and ROX-Session. It's not an AppDir. Best regards, Tilo From riemer at ppprs1.phy.tu-dresden.de Mon Feb 2 20:51:48 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Mon, 2 Feb 2004 21:51:48 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <401E9504.3020904@varlock.com> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> <1075742348.543.14.camel@Horst.wg.lan> <401E9504.3020904@varlock.com> Message-ID: <20040202205148.GB6675@ppprs1.phy.tu-dresden.de> Hello, On Mon, Feb 02, 2004 at 07:20:52PM +0100, Simone Rota wrote: > I'd prefer to use /usr/share/Apps too > (and if needed /usr/share/Choices, etc.) > That would go against CRUX/CLC package policies, Sometime ago I asked Per about right place for ROX apps. He supposed /usr/ROX/apps... But I saw existing ports which install in /usr/share/rox. But however AppDirs are designed to reside anywhere. We must only decide where. > but I think it's a necessary step since one of ROX > main characteristics is the filesystem layout itself. But the layout depends from relative pathes. The place in the file system is not important, only the internal structure. > If there are no objections I'll begin working > on ROX ports tonight. (change fs layout, general cleaning > and testing). > I no longer use ROX-Session, but I'll try to move it > to contrib, for completeness. sounds nice. I can update the lincvs ports then. btw: am I a CLC maintainer or not? If yes how can I contribute my ports (lincvs of course + some others like jikes). Best regards, Tilo From jw at tks6.net Tue Feb 3 08:46:50 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Tue, 3 Feb 2004 09:46:50 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <20040202205148.GB6675@ppprs1.phy.tu-dresden.de> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> <1075742348.543.14.camel@Horst.wg.lan> <401E9504.3020904@varlock.com> <20040202205148.GB6675@ppprs1.phy.tu-dresden.de> Message-ID: <20040203084650.GA1625@hoc> Hi Tilo, On Mon, Feb 02, 2004 at 21:51:48 +0100, Tilo Riemer wrote: > Hello, [...] > btw: > am I a CLC maintainer or not? > If yes how can I contribute my ports (lincvs of course + some others like > jikes). Well, usually, you should know that best (together with Martin...). Did you get a confirmation e-mail regarding creation of your account? You can have a look at http://clc.berlios.de/doc/maintainer-guide.html to find out about the usual way we recruit maintainers: 1. application 2. advocacy (someone votes for you to be on the team) 3. ID: we want to know who you are If you send an application also containing ID info, someone _might_ consider to be your advocate (even if your application is correct, there are sometimes reasons not to accept new maintainers, for several reasons). Chances that you got your account without formal application and advocacy are pretty low (and I haven't found anything like this in my mailbox). Regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From riemer at ppprs1.phy.tu-dresden.de Tue Feb 3 09:35:38 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Tue, 3 Feb 2004 10:35:38 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <20040203084650.GA1625@hoc> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> <1075742348.543.14.camel@Horst.wg.lan> <401E9504.3020904@varlock.com> <20040202205148.GB6675@ppprs1.phy.tu-dresden.de> <20040203084650.GA1625@hoc> Message-ID: <20040203093538.GA23855@ppprs1.phy.tu-dresden.de> Hello Johannes, On Tue, Feb 03, 2004 at 09:46:50AM +0100, Johannes Winkelmann wrote: > Well, usually, you should know that best (together with Martin...). Did > you get a confirmation e-mail regarding creation of your account? No, I didn't. > 1. application I have sent they: lincvs, jikes, galculator. I have made some other ports but I must look if I can/want to hold they uptodate. > 2. advocacy (someone votes for you to be on the team) There are comments that the ports are ok. > 3. ID: we want to know who you are look here: www.lincvs.org What exactly do you want to know? name: known city: Dresden country: Germany prof.: software developer more? Best regards, Tilo From jw at tks6.net Tue Feb 3 10:23:41 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Tue, 3 Feb 2004 11:23:41 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <20040203093538.GA23855@ppprs1.phy.tu-dresden.de> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> <1075742348.543.14.camel@Horst.wg.lan> <401E9504.3020904@varlock.com> <20040202205148.GB6675@ppprs1.phy.tu-dresden.de> <20040203084650.GA1625@hoc> <20040203093538.GA23855@ppprs1.phy.tu-dresden.de> Message-ID: <20040203102341.GA6228@hoc> Hey, On Tue, Feb 03, 2004 at 10:35:38 +0100, Tilo Riemer wrote: > Hello Johannes, > > On Tue, Feb 03, 2004 at 09:46:50AM +0100, Johannes Winkelmann wrote: > > Well, usually, you should know that best (together with Martin...). Did > > you get a confirmation e-mail regarding creation of your account? > > No, I didn't. mmmh, then I'd say you're not a CLC maintainer... > > 1. application > > I have sent they: lincvs, jikes, galculator. Those are ports. An application is a "Bewerbung" in german, so you'd want to write something like "I'd like to become a maintainer for CLC". Either you create ports and wait for us to ask you, or you ask us to accept you as a maintainer. Don't create ports and ask us whether you're already a maintainer. > > 2. advocacy (someone votes for you to be on the team) > > There are comments that the ports are ok. Yes, true. There are no comments that your application is ok, since there was no application (see above) > > 3. ID: we want to know who you are > > look here: > www.lincvs.org > > What exactly do you want to know? > > name: known > city: Dresden > country: Germany > prof.: software developer That's pretty ok... the idea is to have a certain feeling of the person behind the data... certainly a personal website would be nice, but it's not a must. Just note that we can only judge your team ability by your posts to clc-devel. Adding some personal information can only help. I know I'm being annyoing here, but we don't want to become a project with an administration team, so please try to follow the schema mentioned in the "maintainer guide" as closely as possible. Ability to understand the way we work and find related documentation (e.g. the CVS howto) certainly helps to convince us that one's a good candidate. Rest assured that you'll when you've become a CLC maintainer. Regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From riemer at ppprs1.phy.tu-dresden.de Tue Feb 3 11:17:08 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Tue, 3 Feb 2004 12:17:08 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <20040203102341.GA6228@hoc> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> <1075742348.543.14.camel@Horst.wg.lan> <401E9504.3020904@varlock.com> <20040202205148.GB6675@ppprs1.phy.tu-dresden.de> <20040203084650.GA1625@hoc> <20040203093538.GA23855@ppprs1.phy.tu-dresden.de> <20040203102341.GA6228@hoc> Message-ID: <20040203111708.GA27953@ppprs1.phy.tu-dresden.de> Hello Johannes, On Tue, Feb 03, 2004 at 11:23:41AM +0100, Johannes Winkelmann wrote: > mmmh, then I'd say you're not a CLC maintainer... sounds logical ;-) > Those are ports. An application is a "Bewerbung" in german, so you'd > want to write something like "I'd like to become a maintainer for CLC". *ooops* You (that means I) read what you want to read ;-) typical Denglisch problem... > Either you create ports and wait for us to ask you, or you ask us to > accept you as a maintainer. Don't create ports and ask us whether you're > already a maintainer. Ok, ok, I understand now. Sorry for inconvenience. > > look here: > > www.lincvs.org > > > > What exactly do you want to know? > > > > name: known > > city: Dresden > > country: Germany > > prof.: software developer > That's pretty ok... the idea is to have a certain feeling of the person > behind the data... certainly a personal website would be nice, but it's > not a must. I have only project websites. here is the address of my other small projects: www.iapp.de/~riemer/projects I don't have a personal website because I see no sense in it. > Just note that we can only judge your team ability by your > posts to clc-devel. Adding some personal information can only help. See my application ;-) Best regards, Tilo From riemer at ppprs1.phy.tu-dresden.de Tue Feb 3 11:24:46 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Tue, 3 Feb 2004 12:24:46 +0100 Subject: [clc-devel] Application Message-ID: <20040203112446.GB27953@ppprs1.phy.tu-dresden.de> Hello, I'd like to become a maintainer for CLC. Some facts of me: name: Tilo Riemer city: Dresden country: Germany age: 35 prof.: software developer I use Linux (and other Unixes) for 7 years. I have started with SuSE, switched to FreeBSD and - with CRUX 1.1 - back to Linux. CRUX is the first system which makes me happy all the time. The best is the ingenious Ports system. I'm the founder and maintainer of the LinCVS project. LinCVS is a graphical cvs client running on Unix, Windows and Mac OSX. See http://www.lincvs.org or http://www.lincvs.de. I have also started some small projects. See here for more informations: http://www.iapp.de/~riemer/projects. Best regards, Tilo From riemer at ppprs1.phy.tu-dresden.de Tue Feb 3 11:30:45 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Tue, 3 Feb 2004 12:30:45 +0100 Subject: [clc-devel] Application In-Reply-To: <20040203112446.GB27953@ppprs1.phy.tu-dresden.de> References: <20040203112446.GB27953@ppprs1.phy.tu-dresden.de> Message-ID: <20040203113045.GA28307@ppprs1.phy.tu-dresden.de> Hello, here the list of my ports and the URLs: lincvs (http://www.iapp.de/~trogisch/lincvs/download/20_LinCVS/hp_lincvs-1.3.0/lincvs-1.3.0-0-CRUX-port.tgz) jikes galculator (http://ppprs1.phy.tu-dresden.de/~riemer/CRUX-Ports/) Best regards, Tilo From tillbiedermann at yahoo.de Tue Feb 3 11:34:31 2004 From: tillbiedermann at yahoo.de (Till Biedermann) Date: Tue, 03 Feb 2004 12:34:31 +0100 Subject: [clc-devel] ports-database at tbmnet.de Message-ID: <1075808071.2854.17.camel@Horst.wg.lan> Hi, Because a heavy bug in the easy-update function the database got corrupted so that the 'get-it' links doesnt work anymore. But i fixed this problem. I also fixed the SQL-errors when the description field contains special-chars. I also noticed another problem: when you change the pathes, directorynames or repositorynames the easy-updatefunction cant notice that, because it catches all repository-information from the database. In this case you must submit the URL of the httpup-file, so that the database gets the new pathes. And there is still a problem with the unmaintained repository: fopen(http://clc.berlios.de/ports/UNMAINTAINED/unmaintained/syslog-ng/Pkgfile): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found Regards Till -- http://www.tbmnet.de From sip at varlock.com Tue Feb 3 13:14:47 2004 From: sip at varlock.com (Simone Rota) Date: Tue, 03 Feb 2004 14:14:47 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <401E9504.3020904@varlock.com> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> <20040202135039.GC19867@ppprs1.phy.tu-dresden.de> <1075742348.543.14.camel@Horst.wg.lan> <401E9504.3020904@varlock.com> Message-ID: <401F9EC7.2030001@varlock.com> On 02/02/04 19:20 Simone Rota wrote: > If there are no objections I'll begin working > on ROX ports tonight. (change fs layout, general cleaning > and testing). > I no longer use ROX-Session, but I'll try to move it > to contrib, for completeness. Hi, I've just updated rox and apps to use the /usr/ROX basedir (and fixed some other issue I noticed during updates). I didn't have the time to take on rox-session though. I had a lot of troubles during these days with my new AMD machine + kernel 2.6.whatever + nForce2 chipset. I tried just about every suggested solution I found on the net with no success... I had to revert to 2.4 I won't describe the random lockup nightmares ha[ppening since friday. Back on topic, I hope the new ports are ok, if not please let me know. If there's some issue It would be great to send me a patch, since I'm afraid I'll be battling with this machine during the next days. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com From riemer at ppprs1.phy.tu-dresden.de Tue Feb 3 13:52:57 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Tue, 3 Feb 2004 14:52:57 +0100 Subject: [clc-devel] ROX-ports In-Reply-To: <1075726920.2220.21.camel@Horst.wg.lan> References: <20040202083642.GC7185@ppprs1.phy.tu-dresden.de> <1075726920.2220.21.camel@Horst.wg.lan> Message-ID: <20040203135257.GA410@ppprs1.phy.tu-dresden.de> Hello, On Mon, Feb 02, 2004 at 02:02:01PM +0100, Till Biedermann wrote: > i agree. I suggest to have an 'official' AppDir in Crux for AppDir > styles programs. The executables could have a link or a startscript in > /usr/bin for programs that dont know how to handle AppDirs. I have overread... a link does not work in the most cases. The binary inside the AppDir must called with the right absolute or relative path which is not the case if it's called via link. Therefore we must use startscripts. Best regards, Tilo -- Tilo Riemer mailto:riemer at lincvs.org Dresden, Germany http://www.lincvs.org http://www.iapp.de/~riemer/projects From Juergen.Daubert at t-online.de Tue Feb 3 17:33:10 2004 From: Juergen.Daubert at t-online.de (Juergen Daubert) Date: Tue, 3 Feb 2004 18:33:10 +0100 Subject: [clc-devel] new port of LinCVS In-Reply-To: <20040202083305.GA7185@ppprs1.phy.tu-dresden.de> References: <20040202083305.GA7185@ppprs1.phy.tu-dresden.de> Message-ID: <20040203173309.GA1427@jue.netz> On Mon, Feb 02, 2004 at 09:33:05AM +0100, Tilo Riemer wrote: > Hello, Hi Tilo, > a new port of current LinCVS 1.3.0 is available and attached. thanks. After some corrections (fix ownership of files, remove unneeded files, some cleanup in Pkgfile), I've updated the CLC lincvs port to 1.3.0. This time I keep the rox related stuff, because the required rox port is now available in contrib, thanks to Simone for that. Greetings J?rgen -- juergen.daubert at t-online.de From riemer at ppprs1.phy.tu-dresden.de Tue Feb 3 20:20:26 2004 From: riemer at ppprs1.phy.tu-dresden.de (Tilo Riemer) Date: Tue, 3 Feb 2004 21:20:26 +0100 Subject: [clc-devel] new port of LinCVS In-Reply-To: <20040203173309.GA1427@jue.netz> References: <20040202083305.GA7185@ppprs1.phy.tu-dresden.de> <20040203173309.GA1427@jue.netz> Message-ID: <20040203202026.GA13350@ppprs1.phy.tu-dresden.de> Hello J?rgen, On Tue, Feb 03, 2004 at 06:33:10PM +0100, Juergen Daubert wrote: > thanks. After some corrections (fix ownership of files, remove > unneeded files, some cleanup in Pkgfile), I've updated the CLC > lincvs port to 1.3.0. Thanks :-) But could you correct the path in the startscript also? Instead of this line echo exec /usr/share/rox/LinCVS/AppRun '"$@"' > $PKG/usr/bin/lincvs it must be this line: echo exec /usr/ROX/Apps/LinCVS/AppRun '"$@"' > $PKG/usr/bin/lincvs because the new ROX base dir is /usr/ROX/Apps Best regards, Tilo -- Tilo Riemer mailto:riemer at lincvs.org Dresden, Germany http://www.lincvs.org http://www.iapp.de/~riemer/projects From Juergen.Daubert at t-online.de Wed Feb 4 06:32:20 2004 From: Juergen.Daubert at t-online.de (Juergen Daubert) Date: Wed, 4 Feb 2004 07:32:20 +0100 Subject: [clc-devel] new port of LinCVS In-Reply-To: <20040203202026.GA13350@ppprs1.phy.tu-dresden.de> References: <20040202083305.GA7185@ppprs1.phy.tu-dresden.de> <20040203173309.GA1427@jue.netz> <20040203202026.GA13350@ppprs1.phy.tu-dresden.de> Message-ID: <20040204063220.GA267@jue.netz> On Tue, Feb 03, 2004 at 09:20:26PM +0100, Tilo Riemer wrote: [...] > it must be this line: > echo exec /usr/ROX/Apps/LinCVS/AppRun '"$@"' > $PKG/usr/bin/lincvs > > because the new ROX base dir is /usr/ROX/Apps Thanks, I forgot, is fixed now. Greetings J?rgen -- juergen.daubert at t-online.de From jw at tks6.net Wed Feb 11 08:39:46 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Wed, 11 Feb 2004 09:39:46 +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: <20040211083946.GB485@hoc> Hey, On Fri, Jan 30, 2004 at 09:45:15 +0100, Johannes Winkelmann wrote: > 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. OK, I removed it now. > > Another option is to separate the ports (see firebird-acroread-plugin). > Well, this could be an option :-) Certainly looks cool. Should we use a common plugin structure (/usr/lib/java/plugins/) so such a plugin could work with both j2sdk and j2re? this way, it could depend on j2re (so plugin users have a minimal download), while developer who probably understand that j2re is included in j2sdk is fine too? Opinions? Regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From sip at varlock.com Wed Feb 11 13:00:41 2004 From: sip at varlock.com (Simone Rota) Date: Wed, 11 Feb 2004 14:00:41 +0100 Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link In-Reply-To: <20040211083946.GB485@hoc> References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc> <20040211083946.GB485@hoc> Message-ID: <402A2779.7080104@varlock.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/11/04 09:39 Johannes Winkelmann wrote: | Hey, Hi Johannes, |>Note: j2sdk still creates a symlink in /usr/lib/mozilla/plugins. | | OK, I removed it now. Uhm, I see an empty .footprint. Someting wrong with the update :)? |>>Another option is to separate the ports (see firebird-acroread-plugin). |> |>Well, this could be an option :-) Certainly looks cool. | | Should we use a common plugin structure (/usr/lib/java/plugins/) so such | a plugin could work with both j2sdk and j2re? this way, it could depend | on j2re (so plugin users have a minimal download), while developer who | probably understand that j2re is included in j2sdk is fine too? | | Opinions? | Regards, Johannes The idea of a single plugin instead of two as I suggested before is fine for me. I won't change paths in j2(whatever) ports, but make the firefox plugin something like this: if there's j2re links to that else if there's j2sdk use that else don't do anything (footprint mismatch) Regards, Simone - -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAKid58+whKqEdwqMRAjpEAJ9/97oliUEatfUOEaa8Ee+mVLR/GACgkB+Q XG3u2YiJTeLsDJXuNQn2E3M= =DZ+J -----END PGP SIGNATURE----- From Juergen.Daubert at t-online.de Thu Feb 12 07:26:37 2004 From: Juergen.Daubert at t-online.de (Juergen Daubert) Date: Thu, 12 Feb 2004 08:26:37 +0100 Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link In-Reply-To: <402A2779.7080104@varlock.com> References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc> <20040211083946.GB485@hoc> <402A2779.7080104@varlock.com> Message-ID: <20040212072637.GA178@jue.netz> On Wed, Feb 11, 2004 at 02:00:41PM +0100, Simone Rota wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 02/11/04 09:39 Johannes Winkelmann wrote: > | Hey, > > Hi Johannes, > > |>Note: j2sdk still creates a symlink in /usr/lib/mozilla/plugins. > | > | OK, I removed it now. Same for j2re > Uhm, I see an empty .footprint. Someting wrong with the update :)? > > |>>Another option is to separate the ports (see firebird-acroread-plugin). > |> > |>Well, this could be an option :-) Certainly looks cool. > | > | Should we use a common plugin structure (/usr/lib/java/plugins/) so such > | a plugin could work with both j2sdk and j2re? this way, it could depend > | on j2re (so plugin users have a minimal download), while developer who > | probably understand that j2re is included in j2sdk is fine too? > | > | Opinions? > | Regards, Johannes > > The idea of a single plugin instead of two as I suggested before is fine > for me. > I won't change paths in j2(whatever) ports, but make the firefox plugin > something like this: > if there's j2re links to that > else if there's j2sdk use that > else don't do anything (footprint mismatch) fine for me Greetings J?rgen -- juergen.daubert at t-online.de From Juergen.Daubert at t-online.de Thu Feb 12 07:26:37 2004 From: Juergen.Daubert at t-online.de (Juergen Daubert) Date: Thu, 12 Feb 2004 08:26:37 +0100 Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link In-Reply-To: <402A2779.7080104@varlock.com> References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc> <20040211083946.GB485@hoc> <402A2779.7080104@varlock.com> Message-ID: <20040212072637.GA178@jue.netz> On Wed, Feb 11, 2004 at 02:00:41PM +0100, Simone Rota wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 02/11/04 09:39 Johannes Winkelmann wrote: > | Hey, > > Hi Johannes, > > |>Note: j2sdk still creates a symlink in /usr/lib/mozilla/plugins. > | > | OK, I removed it now. Same for j2re > Uhm, I see an empty .footprint. Someting wrong with the update :)? > > |>>Another option is to separate the ports (see firebird-acroread-plugin). > |> > |>Well, this could be an option :-) Certainly looks cool. > | > | Should we use a common plugin structure (/usr/lib/java/plugins/) so such > | a plugin could work with both j2sdk and j2re? this way, it could depend > | on j2re (so plugin users have a minimal download), while developer who > | probably understand that j2re is included in j2sdk is fine too? > | > | Opinions? > | Regards, Johannes > > The idea of a single plugin instead of two as I suggested before is fine > for me. > I won't change paths in j2(whatever) ports, but make the firefox plugin > something like this: > if there's j2re links to that > else if there's j2sdk use that > else don't do anything (footprint mismatch) fine for me Greetings J?rgen -- juergen.daubert at t-online.de From sip at varlock.com Thu Feb 12 11:32:07 2004 From: sip at varlock.com (Simone Rota) Date: Thu, 12 Feb 2004 12:32:07 +0100 Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link In-Reply-To: <20040212072637.GA178@jue.netz> References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc> <20040211083946.GB485@hoc> <402A2779.7080104@varlock.com> <20040212072637.GA178@jue.netz> Message-ID: <402B6437.9090700@varlock.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/12/04 08:26 Juergen Daubert wrote: |>I won't change paths in j2(whatever) ports, but make the firefox plugin |>something like this: |>if there's j2re links to that |>else if there's j2sdk use that |>else don't do anything (footprint mismatch) | | | fine for me | Ok, it's in cvs as firefox-java-plugin. I'll tag it contrib when there's a firefox port in opt. Just a couple of notes: - - Had to use Juergen's mythical footprint hack (see ghostscript). - - will j2re become part of contrib? I don't think it's a good ~ thing to have contrib ports depending on unmaintained ones. ~ I see Juergen's name in the Maintainer field, I guess j2re ~ is a "more maintained" than the usual umaintained ports, ~ so it could be ok this way. - - the firefox-java-plugin could fail to build if there are both ~ j2re and j2sdk installed, depending on the order of installation, ~ since they both link /usr/lib/java. While it's possible to see ~ what port has precedence, I feel it's unnecessary for the moment. Regards, Simone - -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAK2Q38+whKqEdwqMRAum4AJoDyqDYWvS2T3yWEgt3bCJV3+iLhQCfevM3 Q9f/bdMK2YeeHEuCv6wvyVc= =55al -----END PGP SIGNATURE----- From jw at tks6.net Thu Feb 12 11:35:34 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Thu, 12 Feb 2004 12:35:34 +0100 Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link In-Reply-To: <402B6437.9090700@varlock.com> References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc> <20040211083946.GB485@hoc> <402A2779.7080104@varlock.com> <20040212072637.GA178@jue.netz> <402B6437.9090700@varlock.com> Message-ID: <20040212113534.GA5011@hoc> Hi Simone, On Thu, Feb 12, 2004 at 12:32:07 +0100, Simone Rota wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 02/12/04 08:26 Juergen Daubert wrote: > > |>I won't change paths in j2(whatever) ports, but make the firefox plugin > |>something like this: > |>if there's j2re links to that > |>else if there's j2sdk use that > |>else don't do anything (footprint mismatch) > | > | > | fine for me > | > > Ok, it's in cvs as firefox-java-plugin. I'll tag it > contrib when there's a firefox port in opt. Great, thanks! jw -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From Juergen.Daubert at t-online.de Thu Feb 12 17:00:32 2004 From: Juergen.Daubert at t-online.de (Juergen Daubert) Date: Thu, 12 Feb 2004 18:00:32 +0100 Subject: [clc-devel] Re: [bug report] j2sdk: remove/change mozilla plugin link In-Reply-To: <402B6437.9090700@varlock.com> References: <20040130045845.23057.qmail@rfhpc8082.fh-regensburg.de> <20040130084515.GA946@hoc> <20040211083946.GB485@hoc> <402A2779.7080104@varlock.com> <20040212072637.GA178@jue.netz> <402B6437.9090700@varlock.com> Message-ID: <20040212170032.GA186@jue.netz> On Thu, Feb 12, 2004 at 12:32:07PM +0100, Simone Rota wrote: [...] > Ok, it's in cvs as firefox-java-plugin. I'll tag it > contrib when there's a firefox port in opt. Thanks ! > Just a couple of notes: > > - - Had to use Juergen's mythical footprint hack (see ghostscript). > > - - will j2re become part of contrib? I don't think it's a good > ~ thing to have contrib ports depending on unmaintained ones. > ~ I see Juergen's name in the Maintainer field, I guess j2re > ~ is a "more maintained" than the usual umaintained ports, > ~ so it could be ok this way. Yep, you're rigth ;) But in this case that's not fine, I'll move the port to contrib. Greetings J?rgen -- juergen.daubert at t-online.de From jw at tks6.net Thu Feb 12 17:52:58 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Thu, 12 Feb 2004 18:52:58 +0100 Subject: [clc-devel] Documentation: Maintainer Guidelines Message-ID: <20040212175258.GB5011@hoc> Hello, As mentioned some time ago Ian Armstrong has joined our team as a documentation writer. Being busy lately, it took me a lot longer to finally start defining possible work, I'm sorry for that. I haven't talked to Ian a lot about the procedure of requesting changes to documents, and I think it's best to discuss this here in clc-devel. My idea is that we should always consider the current version of a document and collect missing, unclear or wrong parts. Ian can then proceed to create an improved version. Depending on your wishes, Ian, we can also create separate CVSTrac (Bug tracking) categories to coordinate this, and prepare documents in CVSTrac's Wiki. The first thing I'd like to be rewritten are the maintainer guidelines http://clc.berlios.de/doc/maintainer-guide.html So everyone is invited to send comments to this document. Note that this is not about the maintainer selection process itself but the document describing it. I'm looking forward to all your comments. Best regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From victord at jafa.homeip.net Thu Feb 12 18:41:53 2004 From: victord at jafa.homeip.net (Victor) Date: Thu, 12 Feb 2004 13:41:53 -0500 Subject: [clc-devel] Documentation: Maintainer Guidelines In-Reply-To: <20040212175258.GB5011@hoc> References: <20040212175258.GB5011@hoc> Message-ID: <402BC8F1.7000600@jafa.homeip.net> Johannes Winkelmann wrote: > Hello, > > As mentioned some time ago Ian Armstrong has joined our team as a > documentation writer. Being busy lately, it took me a lot longer to > finally start defining possible work, I'm sorry for that. > > I haven't talked to Ian a lot about the procedure of requesting changes > to documents, and I think it's best to discuss this here in clc-devel. > My idea is that we should always consider the current version of a > document and collect missing, unclear or wrong parts. Ian can then > proceed to create an improved version. > > Depending on your wishes, Ian, we can also create separate CVSTrac (Bug > tracking) categories to coordinate this, and prepare documents in > CVSTrac's Wiki. > > The first thing I'd like to be rewritten are the maintainer guidelines > http://clc.berlios.de/doc/maintainer-guide.html > > So everyone is invited to send comments to this document. Note that this > is not about the maintainer selection process itself but the document > describing it. I'm looking forward to all your comments. > > Best regards, Johannes What format will the documentation be in? Could we perhaps define an XML scheme for documentation that can then use XSLT or is that too complex for our purposes? XML data would allow one set of docs to be used in whatever it place it's needed, is that the plan? I have worked with XML, but not so much with XSLT, perhaps someone can comment on complexity of creating XSLT transformation rules and it's pros/cons. Also, how will different languages, if at all, be handled? We should also try to create an automated PUBLISHING process where documentation can be automatically converted to HTML, TXT, and PDF. Another idea is to also create a todo list, that other volunteers can see and if they want, write about something they know and have an email address to submit their work, that Ian can then review and post if it meets guidelines, etc. Victor From sip at varlock.com Thu Feb 12 19:42:26 2004 From: sip at varlock.com (Simone Rota) Date: Thu, 12 Feb 2004 20:42:26 +0100 Subject: [clc-devel] Documentation: Maintainer Guidelines In-Reply-To: <20040212175258.GB5011@hoc> References: <20040212175258.GB5011@hoc> Message-ID: <402BD722.6030600@varlock.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/12/04 18:52 Johannes Winkelmann wrote: [cut] | I haven't talked to Ian a lot about the procedure of requesting changes | to documents, and I think it's best to discuss this here in clc-devel. | My idea is that we should always consider the current version of a | document and collect missing, unclear or wrong parts. Ian can then | proceed to create an improved version. | Depending on your wishes, Ian, we can also create separate CVSTrac (Bug | tracking) categories to coordinate this, and prepare documents in | CVSTrac's Wiki. | | The first thing I'd like to be rewritten are the maintainer guidelines | http://clc.berlios.de/doc/maintainer-guide.html | | So everyone is invited to send comments to this document. Note that this | is not about the maintainer selection process itself but the document | describing it. I'm looking forward to all your comments. | | Best regards, Johannes Hi, As Victor suggested in this thread I think it's important to adopt some sort of standard for the current documentation (btw, my vote goes for docbook). Once we define one or more standards, we're ready for the following tasks: - - Conversion (and update) of existing documents - - Definition of a method for bug submission (you named cvstrac) - - Acceptance of new documents Another thing I'd like is to have all the docs well organized in a cvs module (at berlios.de or at crux.fh-regensburg.de). Back on topic, since you're asking for ideas about the maintainer guidelines, a few points that came into my mind: - - Insert references about httpup repositories (good for training, ~ good when included into an application) - - Make clear that a certain amount of time could pass between ~ an application and the response, since we had some "what happened ~ to my application?" episode in the past. that's all for now, Regards, Simone Regards, Simone - -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAK9ci8+whKqEdwqMRAtyJAKCeESis+/ve0k1Z6ypszaYi6Of2SwCggnMr aTTCA9q+gNAAxKifbM19MlM= =EXaz -----END PGP SIGNATURE----- From jw at tks6.net Fri Feb 13 10:11:42 2004 From: jw at tks6.net (Johannes Winkelmann) Date: Fri, 13 Feb 2004 11:11:42 +0100 Subject: [clc-devel] Documentation: Maintainer Guidelines In-Reply-To: <402BC8F1.7000600@jafa.homeip.net> References: <20040212175258.GB5011@hoc> <402BC8F1.7000600@jafa.homeip.net> Message-ID: <20040213101142.GC566@hoc> Hi Victor, On Thu, Feb 12, 2004 at 13:41:53 -0500, Victor wrote: > Johannes Winkelmann wrote: [...] > What format will the documentation be in? Could we perhaps define an XML > scheme for documentation that can then use XSLT or is that too complex > for our purposes? XML data would allow one set of docs to be used in > whatever it place it's needed, is that the plan? > > I have worked with XML, but not so much with XSLT, perhaps someone can > comment on complexity of creating XSLT transformation rules and it's > pros/cons. XSLT is really cool, and not too hard to learn and use. IMO it's important to adapt a standard like docbook (hi Simone ;-)), but the people who actually write the documentation should decide on that. The CVS HowTo is written in docbook BTW, with customized stylesheets to make it look a bit different than normal docbook docs. A common look would definitely improve the image of CLC. Futhermore, Per uses docbook for the CRUX handbook, and Robert writes the gnome docs in docbook. > Also, how will different languages, if at all, be handled? This is a good question... another thing to remember are the growing number of platforms (ix86, PPC). For the internal documentation at CLC I don't think we need any translations; english is our "business language" after all. > We should also try to create an automated PUBLISHING process where > documentation can be automatically converted to HTML, TXT, and PDF. well, shouldn't be too hard. I write Makefiles for my docbook documents, so a crontab could check out a tagged version and run "make pdf html". I don't think that's important right now though; it doesn't affect the documents themselve. > Another idea is to also create a todo list, that other volunteers can > see and if they want, write about something they know and have an email > address to submit their work, that Ian can then review and post if it > meets guidelines, etc. Yeah, sure. Some new categories in CVSTrac could help us to get started with it. We should make a difference between handy notes which fit better in a Wiki (e.g. notes on upgrading to 2.6) and CLC documentation (e.g. on projects etc). Regards, Johannes -- Johannes Winkelmann mailto:jw at tks6.net Bern, Switzerland http://jw.tks6.net From rrm3 at rrm3.org Mon Feb 23 05:00:08 2004 From: rrm3 at rrm3.org (Robert McMeekin) Date: Mon, 23 Feb 2004 00:00:08 -0500 Subject: [clc-devel] GNOME 2.6 plans Message-ID: <1077512408.4372.24.camel@wodni.local> After committing those last slew of updates to the GNOME ports, I'm now starting to build the GNOME 2.5 branch from scratch (getting ready for GNOME 2.6). I'd rather not worry about updates to the GNOME 2.4 branch now, since I'm not going to have it installed anymore. I hope someone will volunteer to send/commit any critical updates until GNOME 2.6 is released. Per: I would like to time things so GNOME 2.6 is in the ports tree soon after GTK+ 2.4 is in opt (not like last time when I committed everything too soon ;-). This will be simple if you're planning on updating GTK+ in a CRUX release (as opposed to in between CRUX releases). I guess that would be good since things will need to be recompiled against the new GTK+? Anyway, if you keep me informed I'll try and time everything just right. :-) -- Robert McMeekin -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From rrm3 at rrm3.org Mon Feb 23 10:50:21 2004 From: rrm3 at rrm3.org (Robert McMeekin) Date: Mon, 23 Feb 2004 05:50:21 -0500 Subject: [clc-devel] Documentation: Maintainer Guidelines In-Reply-To: <20040213101142.GC566@hoc> References: <20040212175258.GB5011@hoc> <402BC8F1.7000600@jafa.homeip.net> <20040213101142.GC566@hoc> Message-ID: <1077533420.26877.3.camel@wodni.local> On Fri, 2004-02-13 at 11:11 +0100, Johannes Winkelmann wrote: > On Thu, Feb 12, 2004 at 13:41:53 -0500, Victor wrote: > > Johannes Winkelmann wrote: [snip] > XSLT is really cool, and not too hard to learn and use. IMO it's > important to adapt a standard like docbook (hi Simone ;-)), but the > people who actually write the documentation should decide on that. > > The CVS HowTo is written in docbook BTW, with customized stylesheets to > make it look a bit different than normal docbook docs. A common look > would definitely improve the image of CLC. > > Futhermore, Per uses docbook for the CRUX handbook, and Robert writes > the gnome docs in docbook. Do you guys want me to add the FreeBSD stylesheets to the docbook-xsl port? ;-) -- Robert McMeekin From victord at jafa.homeip.net Wed Feb 25 14:33:44 2004 From: victord at jafa.homeip.net (Victor) Date: Wed, 25 Feb 2004 09:33:44 -0500 Subject: [clc-devel] GNOME 2.6 plans In-Reply-To: <1077512408.4372.24.camel@wodni.local> References: <1077512408.4372.24.camel@wodni.local> Message-ID: <403CB248.1000801@jafa.homeip.net> Robert McMeekin wrote: > After committing those last slew of updates to the GNOME ports, I'm now > starting to build the GNOME 2.5 branch from scratch (getting ready for > GNOME 2.6). I'd rather not worry about updates to the GNOME 2.4 branch > now, since I'm not going to have it installed anymore. I hope someone > will volunteer to send/commit any critical updates until GNOME 2.6 is > released. > > Per: I would like to time things so GNOME 2.6 is in the ports tree soon > after GTK+ 2.4 is in opt (not like last time when I committed everything > too soon ;-). This will be simple if you're planning on updating GTK+ > in a CRUX release (as opposed to in between CRUX releases). I guess > that would be good since things will need to be recompiled against the > new GTK+? Anyway, if you keep me informed I'll try and time everything > just right. :-) Hey, Robert. Great work. What's new in 2.6? And are there screenshots of it? Thanks Victor From per at fukt.bth.se Wed Feb 25 15:37:53 2004 From: per at fukt.bth.se (Per Liden) Date: Wed, 25 Feb 2004 16:37:53 +0100 (CET) Subject: [clc-devel] GNOME 2.6 plans In-Reply-To: <1077512408.4372.24.camel@wodni.local> Message-ID: On Mon, 23 Feb 2004, Robert McMeekin wrote: [...] > Per: I would like to time things so GNOME 2.6 is in the ports tree soon > after GTK+ 2.4 is in opt (not like last time when I committed everything > too soon ;-). This will be simple if you're planning on updating GTK+ > in a CRUX release (as opposed to in between CRUX releases). I guess > that would be good since things will need to be recompiled against the > new GTK+? Yep, that sounds good. I haven't looked at gtk 2.3/2.4 yet, so I don't know how compatible it is with gtk 2.2, but I assume gtk apps will need to be rebuilt against the new version. If that assumption is correct I will not upgrade to gtk 2.4 in the crux 1.3 stable tree. Instead gtk 2.4 will have to wait until CRUX 2.0 (if 2.4-final has been released by then). > Anyway, if you keep me informed I'll try and time everything just > right. :-) Sure, I will do my best. All I know at the moment is that CRUX 2.0 is still some time away. For the past month and for some time to come I'm working Monday-Thursday in a different city so CRUX development is a bit slow. I fly back home over the weekends and try to catch up ;) /Per From rrm3 at rrm3.org Fri Feb 27 12:41:05 2004 From: rrm3 at rrm3.org (Robert McMeekin) Date: Fri, 27 Feb 2004 07:41:05 -0500 Subject: [clc-devel] GNOME 2.6 plans In-Reply-To: <403CB248.1000801@jafa.homeip.net> References: <1077512408.4372.24.camel@wodni.local> <403CB248.1000801@jafa.homeip.net> Message-ID: <1077885665.660.8.camel@wodni.local> On Wed, 2004-02-25 at 09:33, Victor wrote: > Hey, Robert. Great work. What's new in 2.6? And are there screenshots > of it? Thanks. In 2.6 we can look forward to more dependencies and a big switch to GTK+ 2.4 (which is bound to introduce some new bugs ;). I'll put up some screen shots sooner or later, but so far 2.6 looks remarkably similar to 2.4. :-/ But seriously when I get a little bit more organized I'll try and put together a nice email to the list about how great 2.6 is. :-) -- Robert McMeekin From per at fukt.bth.se Fri Feb 27 14:39:03 2004 From: per at fukt.bth.se (Per Liden) Date: Fri, 27 Feb 2004 15:39:03 +0100 (CET) Subject: [clc-devel] GNOME 2.6 plans In-Reply-To: Message-ID: On Wed, 25 Feb 2004, Per Liden wrote: [...] > Yep, that sounds good. I haven't looked at gtk 2.3/2.4 yet, so I don't > know how compatible it is with gtk 2.2, but I assume gtk apps will need to > be rebuilt against the new version. If that assumption is correct I will > not upgrade to gtk 2.4 in the crux 1.3 stable tree. Instead gtk 2.4 will > have to wait until CRUX 2.0 (if 2.4-final has been released by then). Hmm, according to http://gtk.org/plan/ the 2.3/2.4 releases are source and binary compatible with 2.0/2.2. /Per From Juergen.Daubert at t-online.de Fri Feb 27 15:46:19 2004 From: Juergen.Daubert at t-online.de (Juergen Daubert) Date: Fri, 27 Feb 2004 16:46:19 +0100 Subject: [clc-devel] opt dependencies Message-ID: <20040227154618.GA6998@jue.netz> Hi all, driven by some questions regarding dependencies of opt ports on #crux, I've spent an hour to put together such a list. Some remarks: - only deps to opt ports are listed - the list is max. compressed, that mean if port A depends on B and C, but B depends on C, only B is listed for A - should be checked for errors ;) Useful ? Should we publish such a list on CLC ? prt-get ? btw, Per, I see one dependency problem in the base ports, vim, because gvim depends on gtk2 which is an opt port. One solution might be to split the port into two, vim and gvim. The first contains most of the stuff, gvim mainly the gvim binary and, of course, depends on / needs vim and should be located in opt or even contrib. kind regards J?rgen Port | Depends on ------------|------------------------------------- atk | glib2 audiofile | pkgconfig cvs | openssl emacs | xfree86 libtiff esound | audiofile fetchmail | openssl firefox | gtk2 libidl fontconfig | freetype2 expat pkgconfig gdk-pixbuf | gtk libtiff glib2 | gettext pkgconfig gtk | glib xfree86 gtk2 | atk pango imlib | xfree86 libtiff libungif libidl | glib2 libogg | pkgconfig libpng | pkgconfig libtiff | libjpeg libvorbis | libogg openssh | openssl pango | glib2 xfree86 pine | openssl ppp | openssl webfs | openssl wmaker | xfree86 libtiff libungif xchat | gtk2 openssl xfree86 | fontconfig libpng xmms | gtk libvorbis esound -- juergen.daubert at t-online.de From rrm3 at rrm3.org Sat Feb 28 12:54:03 2004 From: rrm3 at rrm3.org (Robert McMeekin) Date: Sat, 28 Feb 2004 07:54:03 -0500 Subject: [clc-devel] GNOME 2.6 plans In-Reply-To: References: Message-ID: <1077972843.5451.3.camel@wodni.local> On Fri, 2004-02-27 at 09:39, Per Liden wrote: > Hmm, according to http://gtk.org/plan/ the 2.3/2.4 releases are source > and > binary compatible with 2.0/2.2. Okay. I'll be on my toes then. :-) -- Robert McMeekin From maol at symlink.ch Sat Feb 28 14:26:10 2004 From: maol at symlink.ch (Markus Ackermann) Date: Sat, 28 Feb 2004 15:26:10 +0100 Subject: [clc-devel] update/remove ports from unmaintained Message-ID: <20040228142610.GA622@symlink.ch> Hi Maintainers... please update the gtk-gnutella and realplay ports in unmaintained with the ports available from http://maol.ch/crux/ (httpup). Alternatively you can just delete the ports in unmaintained so people always know where to get the newest version... and you don't have to care about me updating the ports too often. Markus. -- Markus Ackermann http://maol.ch/ http://symlink.ch/ From Juergen.Daubert at t-online.de Sun Feb 29 10:06:19 2004 From: Juergen.Daubert at t-online.de (Juergen Daubert) Date: Sun, 29 Feb 2004 11:06:19 +0100 Subject: [clc-devel] update/remove ports from unmaintained In-Reply-To: <20040228142610.GA622@symlink.ch> References: <20040228142610.GA622@symlink.ch> Message-ID: <20040229100619.GA2447@jue.netz> On Sat, Feb 28, 2004 at 03:26:10PM +0100, Markus Ackermann wrote: > Hi Maintainers... Hi Markus, > please update the gtk-gnutella and realplay ports in unmaintained with > the ports available from http://maol.ch/crux/ (httpup). Thanks ! I've done the updates and moved the ports to contrib also. Greetings J?rgen -- juergen.daubert at t-online.de From maol at symlink.ch Sun Feb 29 10:20:05 2004 From: maol at symlink.ch (Markus Ackermann) Date: Sun, 29 Feb 2004 11:20:05 +0100 Subject: [clc-devel] update/remove ports from unmaintained In-Reply-To: <20040229100619.GA2447@jue.netz> References: <20040228142610.GA622@symlink.ch> <20040229100619.GA2447@jue.netz> Message-ID: <20040229102005.GC622@symlink.ch> Juergen Daubert said|sagte: >Thanks ! I've done the updates and moved the ports to contrib also. Thx a lot. In order to minimize dups I've removed them from my httpup repository. Markus. -- Markus Ackermann http://maol.ch/ http://symlink.ch/ From sip at varlock.com Sun Feb 29 12:41:28 2004 From: sip at varlock.com (Simone Rota) Date: Sun, 29 Feb 2004 13:41:28 +0100 Subject: [clc-devel] opt dependencies In-Reply-To: <20040227154618.GA6998@jue.netz> References: <20040227154618.GA6998@jue.netz> Message-ID: <4041DDF8.9040902@varlock.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/27/04 16:46 Juergen Daubert wrote: | Hi all, | | driven by some questions regarding dependencies of opt ports | on #crux, I've spent an hour to put together such a list. Hi Juergen, (late reply as usual) I did the same some time ago, it took me much more than an hour :) I manually compiled one package at a time form a /base only setup, restarting the process when compilation failed, adding one dep at a time. | Some remarks: | - only deps to opt ports are listed | - the list is max. compressed, that mean if port A depends on | B and C, but B depends on C, only B is listed for A | - should be checked for errors ;) I'll compare with my list and eventually send you diffs and comments, just in case I/you missed something. | Useful ? Should we publish such a list on CLC ? prt-get ? I think it's very useful, expecially for small installations. I expressed myself in the past in favour of adding deps into at least the /opt ports since: - - They're useful for the ones using prt-get - - The ones preferring straight pkgmk / prt-get install ~ are not affected by the dependency add-on So I express my vote for the last time, I won't bother Per or other people any longer on the topic, I promise :-) [cut: Juerge's deps list] Regards, Simone - -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip at varlock.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAQd348+whKqEdwqMRAncKAJ0SiwHmu7pemTnJ2BY5Zgp/ZKECwgCfUQ+q ydz/QVG14XYGYseznCnV8Dw= =0QeO -----END PGP SIGNATURE-----