March 2006 - crux-devel - lists.crux.nu

[clc-devel] CRUX-2.2, glibc-2.3.6, and inotify
by Nick Steeves 19 Mar '06

19 Mar '06

Hi, I'm wondering what everyone thinks of the inclusion of a recent inotify.h into our /usr/include/linux? Gamin works great with it (I've been testing it since Thursday the 2nd, and it seems quite stable--no problems whatsoever), and glibc-2.4 is apparently going to include support for it by default (where applications currently include their own inotify-syscalls.h), so I'm of the opinion that we should add it. Alternatively I can add it to inotify-utils, import that into opt, and inotify-utils can become a dependency for any inotify-capable ports. Cheers, Nick P.S. I'm currently testing the latest version of prelink. It works quite nicely so far--no stability issues, and KDE is quite a bit faster.

2 3

[clc-devel] The road ahead
by Johannes Winkelmann 19 Mar '06

19 Mar '06

Hi there, [ this is rather long. my apologies ] With Per's retirement, I think it's important to take the time and discuss a couple of issues to keep CRUX in shape, and morale up :-). This mail contains a non-exclusive list of things I consider important. I'd like to propose that in the close future (first step), we focus mainly on three things (more on the individual point later in this mail): 1. getting 2.2 out, and having it working well 2. addressing issues we had even with Per on board 3. redistribute Per's work In a second step, let's have CRUXCon 2006 in autumn with as many CRUX devs as possible, and define a common vision for the future. This gives us half a year time to collect ideas and work on prototypes (i.e. for the 3.0 package management as discussed at the former two CRUXCon's). Also, I'd like to propose having weekly or bi-weekly IRC meetings on a defined weekday (i.e. wednesday), to allow slightly more focused discussion and allowing those with less interest to constantly idle on IRC to take part in IRC discussions. Simone suggested to list the dates on a wiki pages, which whould also allow to attach notes like agenda or results; However those meetings are supposed to me non-formal, and attendance is purely optional. ----- Notes on the items from the list: 1. Getting 2.2 out 2.2 is getting close, and we should make sure we have opt tested when we release it. I'm not sure how many of us have a 2.2 test install yet, but I plan to write some notes on how to install it in a chroot to make testing as simple as possible for everyone. We'll also need to update the handbook, and find out where to host the releases (the main file server up to now was fukt, to which no one besides Per has access). 2. Addressing current issues In no particular order: - Add more content to the wiki (howto's etc); we've been discussing this a couple of times already, there seem to be users interested in helping, we need to define some basic structures though to make it usable. This is not critical in general, but frustrating for those who'd like to contribute - write a port validator to detect potentially malicious or dangerous commands in Pkgfiles; run on contrib nightly or so; suggest its use on the relevant wiki pages - move the mailing lists (depends mainly on getting the subscriber lists and archives; I requested those, so as soon as we get them we can do the move). We'll also need list administrators for them - find a maintainer for prtsync (Jay originally wrote it but lacked time/interest, I added a number of quick fixes to address problems appearing during the test runs); there are a number of annoyances, missing features, and things to clean up; nothing too urgent though - define contact persons for certain subsystems; examples for this are: server maintenance, subversion, bug tracking, website accounts, prtsync, mailing list admin, release engineering, user account management and access control. A lot of this stuff currently ends up in my (and probably others') private inbox, which is slightly tiresome. - define a more democratic way do take decisions. Things like the core/opt separation or WiFi kernel module inclusion are typical examples for this, both were basically decided ad hoc on IRC by those online at that point in time. 3. Redistribute Per's work This includes - Per's ports - Handbook maintenance - Release engineering - pkgutils and ports(8) As for pkgutils and ports, there's nothing fundamentally wrong with the two (I know some of the community members tend to have different opinions :-)). However, during CRUXCon 04 and 05, we discussed a lot of ideas which pretty much imply a rewrite of large parts of pkgutils (which was Per's plan initially BTW, however I guess we'll have to take over here). This might be a good moment to collect the quite large number of ideas implemented in the various forks and rewrites, and define a subset of them we want to support in our package management utilities (either directly or by allowing extensions), also considering the various utilities on top of it (pkg-get/pkgsync, prt-utils, prt-get etc.). Obviously, this is a very crucial part of CRUX, and I feel that we should plan that carefully, to get both a powerful and PER/CRUX-like solution. Okay, so much for now, and sorry again for the length. Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Zurich, Switzerland http://jw.tks6.net

6 11

[clc-devel] Release plan for 2.2
by Johannes Winkelmann 18 Mar '06

18 Mar '06

Hi there, 2.2 is getting in shape, so here's the target release plan for it: Mon 20.3. - public release of 2.2-test1 - Stop updating 2.1 except for security related issues - Test your ports on 2.2-test1 - prepare 2.2 release (*) Sat 1.4. - release 2.2 (*) This means: - update the handbook on the website and the ISO - find a solution for the download problem (i.e. find primary download location) - do bug fixes as found by the testers I added a "2.2" version in flyspray, so issues required for 2.2's release should be added there. To check open tasks for 2.2, visit https://crux.nu/bugs/index.php?tasks=all&project=1&&due=3 If you're aware of open issues, please file them in the bug tracker and/or post them here; otherwise, happy testing :-). Regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Zurich, Switzerland http://jw.tks6.net

4 6

[clc-devel] Handbook for 2.2
by Johannes Winkelmann 18 Mar '06

18 Mar '06

Hi there, I've started to update the handbook for 2.2; I'd appreciate if someone could review those changes: http://crux.nu/svnweb/CRUX/revision/?rev=965 Also, I've just editied handbook.xml, install.xml and intro.xml; there's configure.xml, faq.xml (some devfs references), package.xml (add prt-get reference) and ports.xml (should explain new contrib, core etc.) left. I don't plan to work on those for now, so I'd appreciate if anyone else could check those. Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Zurich, Switzerland http://jw.tks6.net

1 0

[clc-devel] Notification from CRUX
by Flyspray 17 Mar '06

17 Mar '06

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. Johannes Winkelmann has taken ownership of the following task: FS#13 - Testing ML notification More information can be found at the following URL: https://crux.nu/bugs/?do=details&id=13 You are receiving this message because you have requested it from the Flyspray bugtracking system. You can be removed from future notifications by visiting the URL shown above.

2 1

[clc-devel] Notification from CRUX
by Flyspray 17 Mar '06

17 Mar '06

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. Johannes Winkelmann has taken ownership of the following task: FS#14 - Testing ML notification, mk. 2 More information can be found at the following URL: https://crux.nu/bugs/?do=details&id=14 You are receiving this message because you have requested it from the Flyspray bugtracking system. You can be removed from future notifications by visiting the URL shown above.

1 0

[clc-devel] Notification from CRUX
by Flyspray 17 Mar '06

17 Mar '06

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this: - Johannes Winkelmann (jw) Attached to Project - CRUX Summary - Testing ML notification, mk. 2 Task Type - Bug Report Category - website Status - New Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - Development Due in Version - Due Date - Undecided Details - Testing notification (only sent when a bug is not assigned to a particular user) More information can be found at the following URL: https://crux.nu/bugs/?do=details&id=14 You are receiving this message because you have requested it from the Flyspray bugtracking system. You can be removed from future notifications by visiting the URL shown above.

1 0

[clc-devel] Notification from CRUX
by Flyspray 17 Mar '06

17 Mar '06

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#13 - Testing ML notification User who did this: - Johannes Winkelmann (jw) Reason for closing: - Not a bug More information can be found at the following URL: https://crux.nu/bugs/?do=details&id=13 You are receiving this message because you have requested it from the Flyspray bugtracking system. You can be removed from future notifications by visiting the URL shown above.

1 0

[clc-devel] Flyspray user account default permissions
by Tilman Sauerbeck 11 Mar '06

11 Mar '06

Hi, the default permissions for newly created user accounts in Flyspray are somewhat silly right now - they aren't allowed to open bugs. OTOH they aren't allowed to 'view tasks' either, but still it's working. I'm confused ;) Simone, can you set the default permissions to more useful values? Please also set my account to developer mode :) Thanks, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?

2 1

[clc-devel] Testing ports in a 2.2 chroot
by Johannes Winkelmann 10 Mar '06

10 Mar '06

Hi there, As promised here's a quick guide on creating a 2.2 chroot to test your ports: http://crux.nu/wikka.php?wakka=ChrootTesting Feel free to fix/adjust that page, and/or add notes. Regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Zurich, Switzerland http://jw.tks6.net

2 2