- crux-devel - lists.crux.nu

[clc-devel] CRUX Hosting
by Per Liden 14 Jun '05

14 Jun '05

Hey Charlie and CLC guys, I'm writing in english and CC'ing the CLC mailinglist so that the CLC-team can also participate in this discussion. First just a short summary to bring the CLC guys up to date. (Charlie, feel free to correct any inaccurates in my summary). Some time ago Charlie asked me if there was something he could do to help the CRUX project. Charlie works at Mitex (an ISP in Kalmar/Sweden that use CRUX on ~30 of their servers) and since the CRUX/CLC project have been looking for alternative hosting for some time I took the opportunity to ask if some kind of dedicated server was possible to arrange. Charlie was quite positive to this and thought it would be possible to make something like this happen. At the time we spoke I was in the middle of releasing CRUX 2.1 (i.e. had lot's to do) so I said I would come back to this once the dust had settled. So, here we are. CRUX 2.1 has been released and now would be a good time to return to the hosting issue. I'd like to start of this discussion by asking you Charlie, first of all, does the offer still stand? If so, could you please make short summary of what kind of hosting you (Mitex?) could provide for the CRUX/CLC project? I'm thinking that things like server/disk capacity, limitations on bandwidth, possible firewalls, root access, general ruls, etc are things of interest to us and a good starting point. kind regards, /Per

2 2

[clc-devel] java-config
by Johannes Winkelmann 13 Jun '05

13 Jun '05

Hi, Another of those things we briefly discussed in Stockholm last year, a script allowing to select a particular java version: http://jw.tks6.net/files/crux/java-config It's a rather quick hack, but should work as advertised. Jay, can you have a look? Regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net

1 0

[clc-devel] joining contrib
by Johannes Winkelmann 13 Jun '05

13 Jun '05

Hi fellow CLC'ers, We're running the test setup for clc-contrib for some time now, and it looks quite good. We'd like to test with more ports though, so if you think the rules are fine (and given that they're less strict that those we have at CLC I think they should be) and want to participate, I'd appreciate if you'd join the testing. Rules here: http://clc.morpheus.net:6999/clc/wiki?p=NewContribRules There's a section called "Requirements for contributors" which is a good starting point if you'd like to avoid reading the whole page. All we need is your e-mail address and <user>.httpup file. Thanks for your interest, Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net

1 1

[clc-devel] Duplicate libgd port
by Torsten Henschel 06 Jun '05

06 Jun '05

Hi, the libgd port is in contrib with version 2.0.33 and in unmaintained with version 2.0.28. Regards Torsten

2 1

[clc-devel] CRUX menu-driven setup
by Simone Rota 05 Jun '05

05 Jun '05

Hi, we're probably going to deploy a good number of CRUX installations where I work, and since I've been requested a more user-friendly setup, today I started to work on a menu based setup program. You can find some screenshot here: http://www.varlock.com/tmp/replisetup/ At the moment I'm evaluating the use of replimenu[1], a very compact (no deps!) and flexible menu drawing program, combined with bash. The general idea is to represent via menus the various steps required by the traditional installation, avoiding to add too much automation. I write to the CLCDEV ML since we briefly spoke about a possible new setup app (subproject?) during CRUXCON 2004 and later on, so I'd like to know if there's already somebody working on this, plus comments and ideas. Regarding the status of the project, I coded most of the GUI stuff today, obtaining a working prototype of a "stateful" setup procedure, which collects all the information necessary for the rest of the script to actually perform the install. I won't have much time next week to spend on this, yet I'll be glad to hear some opinion from clc-devel. Regards, Simone [1] http://replimenu.sf.net -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip(a)varlock.com

1 0

[clc-devel] contrib/opt merge: second thoughts
by Johannes Winkelmann 02 Jun '05

02 Jun '05

Hi, Lately, I'm having second thoughts whether it's a good idea to merge opt and contrib into one collection. Not to be missunderstood, I consider it very important to merge CVS repositories, and CRUX/CLC. But somehow I don't like the idea of having 5 window managers, MTA's, web servers and the like in opt. I've been discussing this with Juergen quickly, and he seemed to agree to that consideration. My suggestion would be to keep a separate category, maybe called 'extra' or something like that, and allow maintainers to suggest ports for addition into opt. Those contrib ports which are currently included on the ISO would certainly make good candidates for that. In the end, we have a need for this distinction anyway, since we couldn't include 'opt' completely an ISO if it was merged with contrib. At CRUXCon 2004, we said we'd introduce a 'core group', marked with an attribute in the Pkgfile. To me, keeping a third collection seems very similar, but easier to understand for users. We'd then have the following hierarchy: - base: ports required to run a crux system - opt: ports required depending on the use of the machine - extra: ports which replace ports from opt (function wise) or extend it - contrib: user contributed ports Bad idea, good idea? Kind regard, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net

8 11

Re: [clc-devel] contrib/opt merge: second thoughts
by Jay Dolan 31 May '05

31 May '05

Hi, I'm not yet convinced that it's entirely necessary. What's the harm in having all of these things in opt? Per will simply decide what comes on the ISO. The rest being there doesn't hurt anyone.. I don't think (?) I'm not saying you're not right. I'm just saying I'm not entirely convinced yet :) Also, why not name this collection, if it comes to fruition, 'clc'? Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail

3 2

Re: [clc-devel] contrib/opt merge: second thoughts
by Jay Dolan 31 May '05

31 May '05

--- Nick Steeves <Nick.Steeves(a)shaw.ca> wrote: > Does the "persistent tags single CVS split into > multiple dirs via cvsup" idea > sound simple and manageable enough? Jonathan Asghar > mentioned splitting up > ports according to function. It seems like we can > probably last another year > without this, but perhaps it might be a good idea > for CRUX-3.0, if our > "CONTRIB: Users" grows significantly? > > Jay: Do you think this functionality could be > implemented the .sync file? > The .sync would be a "sync to where" token. > > Just trying to think about how to keep things > simple, in an increasingly > complex climate. > > Nick > Hi Nick, I'm not sure furthering the purpose of the .sync file is the best idea. I had thought of exactly what you suggest some time ago, but I kinda made myself dismiss it. The "correct" way to achieve that kind of control, in my opinion, would be to use CVS locally for your ports, and make httpup-repgen "CVS-aware." (Catch that, cptn?) Thus, tag ports locally for CONTRIB, OPT, whatever, and tell httpup-repgen to generate a repo for certain tagged versions. But *then* we're just re-implementing cvsup.. I don't know, too complicated - I need a nap. And a cookie. I don't see a reason for all of this worry, to be honest. 1) Find a home for CRUX and CLC projects, setup CVS there. 2) Import CRUX and CLC CVS repositories to the new home. Tag them CRUX-2_1. It's a big collection. So? 3) Bump the ports(8) release number, pack a new .cvsup driver file, alert the mailing lists of the changes. 4) Begin offering the new CONTRIB collection with a few interested httpup maintainers. Barring any disasters, open it up to other maintainers after a few weeks. Everyone gets to continue going about their business for the most part. Per and CLC will have to checkout a new working copy. Users will have to clean their ports tree. Leave the old clc tree online for as long as possible, or tar it up and sweep it under the rug. I don't really care. Flame me for my oversight. We can either hypothesize until the cows come home, or Just do it(r). ;) Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/

1 0

[clc-devel] [CLC Ticket Notification] Updated version for slrn
by crux＠morpheus.net 30 May '05

30 May '05

Assigned to [clc-devel(a)lists.berlios.de] The following CLC ticket (63) has been created or modified: Description: Remarks: Contact: strcat at gmx dot net CLC User: sip Status: closed URL: http://clc.morpheus.net:6999/clc/tktview?tn=63

1 0

[clc-devel] please review: contribution guide
by Johannes Winkelmann 22 May '05

22 May '05

Hi, I've been asked a few times on IRC now how to contribute to "CRUX", and therefore decided to write a short guide about steps towards CLC maintainership: http://clc.morpheus.net:6999/clc/wiki?p=HowToContribute I'd appreciate if you could have a quick look at it, adjust it, fix my typos, word order and grammar errors etc. (it's pretty late here already...). Thanks, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net

1 0