On May 26, 2005 5:46, Johannes Winkelmann wrote:
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.
Why not merge opt and contrib, and then "sticky tag" all the opt ports as OPT? We already have a CLC tag, so perhaps this tag-distinction could be leveraged to our advantage?
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.
I like this idea. Could it be implemented with a persistent tag? To suggest a port for inclusion into OPT, tag it EXTRA, and if one feels that it might require a reason, send an email to Per as well. File.cvsup would split up the large CVS collection into the usual, comfortable collection of directories that make up /usr/ports. Then there no Pkgfile changes are needed. Wouldn't the 'core group' necessitate some kind of parsing function complexity?
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
Ok, so base would remain base. Opt would be a tag. Extra would a tag. CLC is already a tag. Perhaps CLC should go in /usr/ports/clc? Contrib would be user-contributed ports. (this sounds like that "people" collection of a little while ago) So: / / BASE: Per Our CVS / / \ Many ports / OPT:Per EXTRA: Us One root \ \ / Tagged for Sanity. \ CLC: Us \ | \ CONTRIB: Users Will "CONTRIB: Users" and "CLC: Us" be merged in CVS, or in /usr/ports/contrib? What will happen to the CONTRIB-X_Y tag? Will the user's contrib automatically be tagged CONTRIB-X_Y (CURRENT)? Finally, what belongs where? For example, where should I put a very nice QT3 style/theme, or a not-everyone-will-use-this application? (ed2k-gtk-gui, or gnugo, for example) Should it remain in my httpup repo, should it be synced into "CONTRIB: Users"? 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 P.S. I'm not sure if I understand the mechanics of a "sticky tag". It sounds like it would be useful as a persistent marker...