April 2005 - crux-devel - lists.crux.nu

[clc-devel] Roadmap
by Johannes Winkelmann 09 May '05

09 May '05

Hi, I think it's time that we try to come up with a roadmap for the time ahead. There are numerous thing which have been prepared and should be finalized sometimes in the future. The most important ones that come to mind are: 1. New server 2. Structure of the CRUX/CLC project 3. Webpage move/merge (new ports db); things currently missing 4. Short revision control tool discussion (also WRT multiple archs) 5. CVS merge contrib -> opt; core group 6. New contrib collection Less pressing, but also important: - mailing list concept - Introducing subprojects - recruit contributors for subprojects - webpage - ports - tools (self developed stuff) - docs - installer ? - Better responsibilities (kinda goes hand in hand with subprojects) - non-x86 arch handling I added "better responsibilities" since there are certain things which should IMO be defined; e.g. I updated the httpup repos to 2.1, or created the CVS branch for 2.0; both just because I felt it should be done now, and no one else had done it so far (and in the case of httpup people started to wonder...). I don't mind doing those things (also in the future), but I think having a person explicitely in charge would give at least me a better feeling. I'm not sure whether we should organize some IRC/Skype/whatever-meeting or discuss this in the mailing list, but I feel that we should just do it sometimes soon, since there are people actively working on some of these things and I feel bad myself about not providing them more help. So if you have a moment, please take the time to think about the above, and how/whether you'd like to discuss this. Comments appreciated, but not required :-). Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net

4 7

[clc-devel] 2.1 tag for unmaintained ports
by Simone Rota 03 May '05

03 May '05

Hi there, Me, Johannes and Juergen had a brief discussion on IRC regarding ports that one is going to drop for 2.1. Please tag them GRAVEYARD, (not UNMAINTAINED) so people still using the 2.0 ports won't get duplicates in contrib and unmaintained. This could cause a temporary disappearing of some port, but we'll re-integrate them in a httpup repository as soon as the new contrib setup is ready for prime time. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip(a)varlock.com

2 1

[clc-devel] [CLC Ticket Notification] Updated version for centericq
by crux＠morpheus.net 29 Apr '05

29 Apr '05

Assigned to [clc-devel(a)lists.berlios.de] The following CLC ticket (64) has been created or modified: Description: I have a new port for centericq. A u to date version can be found at http://www.strcat.de/crux/ports/ Remarks: Contact: strcat at gmx dot net CLC User: vector Status: fixed URL: http://clc.morpheus.net:6999/clc/tktview?tn=64

1 0

[clc-devel] [CLC Ticket Notification] mjpegtools fails compilation
by crux＠morpheus.net 29 Apr '05

29 Apr '05

Assigned to [clc-devel(a)lists.berlios.de] The following CLC ticket (82) has been created or modified: Description: Remarks: Contact: skodela at skodela dot co dot uk CLC User: anonymous Status: new URL: http://clc.morpheus.net:6999/clc/tktview?tn=82

1 0

[clc-devel] howto documentation
by Johannes Winkelmann 25 Apr '05

25 Apr '05

I just created a page for howtos at http://clc.morpheus.net:6999/clc/wiki?p=HowTos Currently, there's only a PAM howto there, but I'd like to see more coming there (the udev doc for example). So please feel free to add some content there, to make sure we don't forget about this for the new webpage :-). Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net

1 0

Re: [clc-devel] Subversion test repo at clc.berlios.de
by Jay Dolan 20 Apr '05

20 Apr '05

--- Tilman Sauerbeck <tilman(a)code-monkey.de> wrote: > > > Why do we need to specify $COLLECTION in the > blah.svn file? Why not > > > do it the same way httpup handles it (basename > of the ports file minus > > > the extension)? When first writing prtsync, I specified the addition of COLLECTION in .httpup files, but later removed support for it for this same reason you mention. It is rather unnecessary, and leaves room for a little confusion: e.g. "Okay, something's wrong with collection x.. now which driver file is that collection defined in?" 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

[clc-devel] Subversion test repo at clc.berlios.de
by Johannes Winkelmann 19 Apr '05

19 Apr '05

Hi, I've just enabled the crontab job to sync per's base and opt and our contrib to the subversion repository at CLC. The repository can be browsed here: http://svn.berlios.de/viewcvs/clc/x86/tags/CRUX-2_1/ Every change in Per's CVS HEAD and ports tagged as CONTRIB-2_1 should appear there as well. Please complain if they don't (and if you care about it ;-)). Note that the sync is once per hour only. I also wrote a ports(8) driver for subversion, available at http://jw.tks6.net/files/crux/svn.driver Thanks Tilman for testing and suggestions. Finally, the "supfiles" for your /etc/ports: http://jw.tks6.net/files/crux/base.svn http://jw.tks6.net/files/crux/opt.svn http://jw.tks6.net/files/crux/contrib.svn After installing those, ports -u will update from the subversion repository, too. We'll need some more output filtering to make it look just like subversion, but for now I couldn't care less :-). If your svn repository requires username/password, set the 'USER' and 'PASS' variables in your "supfile": URL=https://some.host/svn/repos/ports/trunk COLLECTION=internal ROOT_DIR=/usr/ports/svn USER=joeuser PASS=secret That said, I plan to test importing/merging the sparc tree against this subversion tree soon, hopefully tomorrow, and will write a wiki page describing all this. Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net

3 8

[clc-devel] Phase out as maintainer...
by Opel Martin 18 Apr '05

18 Apr '05

Hi there, I have decided to quit beeing a CLC maintainer due to a lack of time. Please don't be angry, because I tagged lots of ports unmaintained shortly before the Crux 2.1 release, but I don't find the time to maintain them all. I hope my ports find new maintainers. Of course I will stay a enthusiastic CRUX user :) Bye! Martin. -- Martin Opel, mo at obbl-net dot de Regensburg, Germany

4 3

Re: [clc-devel] CRUX/CLC website proposal
by Jay Dolan 18 Apr '05

18 Apr '05

--- Till Biedermann <tillbiedermann(a)yahoo.de> wrote: > The advantage of including all httpups in the > database is that you have > one point where you can search for ports in the > whole CRUX-universe. > > I suggest something like a checkbox "exclude > httpups" in the search > mask. Or favoring CLC-ports in the search result > list. > > I agree with the idea that the portdb on the > CRUX/CLC website should > only list CRUX/CLC ports. But from the point of view > of an average user > it is annoying to have two databases or actually > none for httpups. > Hi all. I'm sorry I've been relatively quiet throughout this discussion. Sip, I *really* like what you've done so far. It's excellent. In regards to the forum, my opinion is rather neutral. It would not bother me if we had one, unless it detracted from the ML and/or caused confusion/redundancy. With respect to subprojects, I would like to see all of our one-off tools bear a project page on the portal. Imo, this includes things like prt-get, yapo, prt-utils, pkgsync, et al. If we are going to promote subproject development, it only makes sense to put our current subprojects into this same place. It would present a more unified vision to users. As far as [a rewritten] portdb is concerned, I think this would be a good time to talk about creating a common c library for manipulating ports and packages. We spoke briefly about this at CC2K4, but I don't know if any progress has been made since. Pkgutils, prt-get, and others could greatly benefit from such a library. It would also allow other projects, like a new portdb, to be developed rapidly. I would be interested in contributing to an effort to produce this. Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail

1 0

[clc-devel] CRUX/CLC website proposal
by Simone Rota 18 Apr '05

18 Apr '05

Hi, I've been working on the new CRUX/CLC site lately, here's some screenshot of a working wikka setup: http://www.varlock.com/tmp/wikka/ Questions time: 1. Ok, apart from Wilber which is a temp thing, do you like the current style? I've also worked on punbb integration (last image) since there's been some request for a forum. 2. Regarding content, I've ported most of the documents on the current CLC and CRUX websites, but there is more to do. Should we setup a working temp site somewhere to fill together the pages before we go live? (then we can transfer the db to the actual site). 3. Integration I briefly spoke with Johannes regarding the integration of the a bug tracker into the website. Will we use cvstrac for this? Other options? Another question is the ports database page: I suppose we should change it a bit to fit the new contrib (do we still want to list the external httpup repos not in contrib?) Comments, ideas and contributions are welcome as usual ;) Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip(a)varlock.com

5 8