May 2005 - 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] 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

[clc-devel] FAQ
by Jonathan Asghar 18 May '05

18 May '05

Hey guys, I'm starting a more complete FAQ for the clc. Ya'll can check out the work in progress at http://tito.homelinux.org/fileserver/faq.html. My question is: What are some FAQs? I'm working on it but figured that should ask anyway. Jonathan Asghar

1 0

[clc-devel] Re: prtsync manpage
by Jay Dolan 16 May '05

16 May '05

--- Nick Steeves <Nick.Steeves(a)shaw.ca> wrote: > Hi Jay, > > Under the sync section of the prtsync manpage, the > email format is specified > as: EMAIL=user(a)provider.net. It should read: > EMAIL=user at provider dot > net, according to those port guideline changes from > earlier this spring. > Here's a bit of code to show what I mean: > > Line 80 > - email=`fgrep "EMAIL=" $driver | sed "s/EMAIL=//"` > + email=`fgrep "EMAIL=" $driver | sed -e > "s/EMAIL=//" -e "s/ at /@/" > + # is there a better way to guarantee $? is 0? > + test 1=1 > + # how should one deal with an unpredictable # of > "dot"? > + while [ $? -eq 0 ]; do > + email=`echo $email | sed "s| dot |.|"` > + echo $email | grep " dot " > /dev/null > +done > url=`fgrep "URL=" $driver | sed "s/URL=//"` > Line 83 > > > Cheers, > Nick > Hi Nick, The EMAIL directive is not required by httpup(8) or ports(8). It's an extension used only by prtsync, only on the CLC server. As this address is never publicly viewed over the web (unlike Pkgfiles), I think leaving it unobscured is perfectly fine. However, if others think it'd be a nice feature, I'll add support for it. I guess people could start supplying EMAIL in their .httpup files, aleviating some of the prtsync maintenance, as I currently add this by hand *g*. Perhaps a slightly cleaner patch: email=`fgrep "EMAIL=" $driver | sed 's|EMAIL=||; s| at |@|; s| dot |\.|'` This would actually allow either address syntax. Thanks for poking into this :) Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Re: [clc-devel] bug day(tm)
by Jay Dolan 16 May '05

16 May '05

--- Johannes Winkelmann <jw(a)tks6.net> wrote: > First off all, I think we haven't managed to discuss > all the items > mentioned on the wiki page, but mainly because the > hosting situation is > not clear at all (on which many of the other tasks > depend). Multiple > efforts so resolve this are ongoing, or will start > this week. I should have a definite answer this week from UMass Dartmouth, as to whether or not they'll host us. > The new contrib collection is online, and as you've > probably read public > testing should start soon, certainly within this > week. HttpUp maintainers interested in participating, please email me your .httpup driver files from the email address you wish to receive clc-contrib@ notifications at. Also, be sure to tag your ports with .sync files. > The 'alias' discussion was not really extensive, but > I guess we'll just > introduce it and see how it feels, since it's > completely restricted to > prt-get at the moment. I plan to make a new release > of prt-get later > this week, or next weekend, incorporating the list > of aliases. Yay :) Can we review the list of aliases before this release? > Jukka has provided lists of ports with broken > sources, and broken > dependencies (deps which are not in contrib): > http://clc.morpheus.net:6999/clc/wiki?p=BrokenSources > > http://clc.morpheus.net:6999/clc/wiki?p=MissingPorts > I you haven't done so, please check those two lists. I'll be adopting netpbm, and have indicated so on the MissingPorts list. If others would do so as well, we can avoid working to replace the same ports twice. > Till Biedermann has given us an update on his work > on a new port > database, which will be fully integrated in the > wiki. Sweet. > Finally, as a general impression, I liked the fact > that it was a focused > meeting and opportunity to discuss issues with > multiple members of CLC. > On the other hand, it was a bit long (three days) > and we had too many > items listed to discuss (well, we have many > outstanding issues, but > still). > > I'd like to hear different opinions, but in general, > I'd consider it a > good idea to do something like this more regularly, > say once per month, > and maybe "just" two days. > Yea, that sounds reasonable. Even every-other-month would be an improvement, and is perhaps a bit more reasonable. 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

1 0

[clc-devel] bug day(tm)
by Johannes Winkelmann 16 May '05

16 May '05

Hi, This is mainly meant for Per and CLC maintainers, but in no way private: Let's see whether this "bug day" is a good thing: the idea is to focus on some more or less burning issues and discuss them in a separate IRC channel (we can always talk about our daily life in #archlinux ;-)). I added the items from the "roadmap" mail to a wiki page, online at http://clc.morpheus.net:6999/clc/wiki?p=BugDayTm Please add/adjust this page at will. If you feel like discussing about those and other issues, please join #crux-bugday, from now until saturday. Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net

1 1