May 2005 - crux-devel - lists.crux.nu

[clc-devel] new contrib rules
by Johannes Winkelmann 16 May '05

16 May '05

Hi, The new contrib collection is entering its real testing phase, thanks to Jay's work setting it up this weekend. I'd like to start public testing really soon now, and I've gone over the rules document to make sure participants understand the goals and consequences thereof. I'd appreciate if those interested of you could read through it, ask questions, make changes, fix typos etc. It's the first part on http://clc.morpheus.net:6999/clc/wiki?p=NewContribRules (the second part was the original doc). As soon as this document is in an okay shape, I'd suggest we start the public testing. I think we should have another meeting _after_ the test phase (or after a while of testing) with both users, non-clc participants und us to see whether our idea is good or not. Thanks for your help, Regards Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net

1 0

[clc-devel] Discussion? sysconfdir settings in CLC ports
by Matt Housh 11 May '05

11 May '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, all. I'd like to start some discussion about explicitly setting sysconfdir (or confdir or whatever the package uses) back to /etc instead of letting the default prefix decide it. I'd love to hear what everyone thinks of this because it's causing me and jdolan at least a few issues. Here's the problem: XDG-compliant apps (freedesktop.org XDG stuff) look for XDG_DATA_DIRS and XDG_CONFIG_DIRS (and possibly XDG_DATA_HOME and XDG_CONFIG_HOME) in the environment and try to use those if they exist. If they do not, /etc/xdg and /usr/share are the defaults. While this doesn't sound like a problem from that small description, graveman and gnome-menus both behave badly under certain circumstances due to these. gnome-menus first: gnome-menus expects to use XDG_CONFIG_DIRS for its menu population. If the environment variables are NOT set, the default /etc/xdg is assumed and you won't see any custom menus or most of the default editable entries in gnome. If the environment variables ARE set, the menus appear correctly. But then graveman doesn't work. graveman uses XDG_DATA_DIRS for its themes/icons/whatever. That would be fine except that there seems to be a bug (posted but not yet acknowledged) in how graveman searches for these files. The port installs files in /usr/share/graveman. If the env vars are not set, these are found. If they ARE set, XDG_DATA_DIRS will be /usr/share but graveman for some reason adds the config file name to that as a directory and goes from there. So you see something like this: stat64("/usr/share/graveman/graveman.conf/themes/default/Menu-Other-48.png", 0xbfffe8a0) = -1 ENOENT (No such file or directory) It's appending "graveman.conf" to an otherwise correct XDG_DATA_DIRS+graveman location. Symlinking graveman.conf to . in /usr/share/graveman will work around this but that's ugly as hell, IMO. Openbox also uses these but it doesn't seem to care whether its XDG configs are in /usr/etc/xdg or /etc/xdg. HOWEVER, if they are in one and the env var is set to the other, menus fail to work as might be expected. So here's what I'm getting at: Why do we use /usr/etc? Is it simply because that's the default when --prefix=/usr is used? If so, does anyone object to setting --sysconfdir=/etc for those apps which honor it? This isn't really a lot of apps, it seems mostly gnome stuff. However, pango and gtk2 at least are included: jaeger::charon::/usr/etc => ls bonobo-activation gnome-lite gnopernicus-1.0 pear.conf esd.conf gnome-vfs-2.0 gtk-2.0 sound gconf gnome-vfs-mime-magic pango xdg pear, esound, pango, gtk appear to be affected but this is still a very small list. I can understand not wanting to put things in /etc that aren't vital to the running of the system but on the other hand, things are starting to fail in weird ways the more apps I install (graveman today was what really brought this to my attention, though). While it seems we can force some things to use /usr/etc/xdg instead of /etc/xdg, others just flat-out don't support a non-default location correctly, from what I'm seeing. Thoughts? - -- Matt Housh (jaeger@freenode/#crux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCe4jnGFVQ7mavvGgRAo6nAJ9Mo9I5asQnepwu4i+OiZPpuLCXSwCfQqsp DNUfai8k/abGfnIL3hSopxk= =cS43 -----END PGP SIGNATURE-----

6 10

Re: [clc-devel] Discussion? sysconfdir settings in CLC ports
by Jay Dolan 11 May '05

11 May '05

--- Juergen Daubert <jue(a)jue.li> wrote: > Sorry, but I guess, that you everything-into-/etc > guys read over one > important point of Nick's mail: > > <quote> > Also, /etc is usually protected because that is > /etc/pkgadd.conf's > default. /usr/etc is usually overwritten with each > release, which > insures that the upgrade works out of the box. > Isn't the latter > preferable to the support nightmare of persistent > configuration files > which might be incompatible in some way with the > upgraded API? > </quote> > > That's at least important for progs like gtk, sane, > mutt, nail etc., > the settings are important for the applications, but > the user shouldn't > ever touch them and they _must_ be overwritten with > new releases. > > kind regards > Juergen > > I agree. While I expressed distress with xdg/gnome-menus problems, I do not feel that /etc is the proper place for all package configurations. In fact, I'd like to see more ports make use of /usr/etc, as things like gdm, cups, and ssh end up requiring lots of rejmerg attention. /etc should be reserved for very essential, and rather static, system config files. *If* a user ends up having to edit something in /usr/etc, he/she should know well enough to make an addition for it in /etc/pkgadd.conf if he/she so desires. Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs

1 0

[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

Re: [clc-devel] Roadmap
by Jay Dolan 09 May '05

09 May '05

--- Simone Rota <sip(a)varlock.com> wrote: > You hope. You've been selected to attend all 3 days > of the > meeting (72 hrs) and *manually* log the chat > sessions > by typing into a text editor. > Copy & paste cheating not allowed. > > Have fun! > Simone > :[ I suppose I deserve this, for making you guys put up with me.. *cracks knuckles* let's get started, then.. ;) Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

1 0

Re: [clc-devel] Roadmap
by Jay Dolan 09 May '05

09 May '05

--- Johannes Winkelmann <jw(a)tks6.net> wrote: > I'd suggest we do a "bug squishing day" inspired by > debian and others, > where we all meet in a special IRC room (#crux-bugs) > to discuss things > like adapting ports from former maintainers, webpage > move and similar > issues. We might also go for a whole weekend to make > sure everyone has > the chance to drop by once. > > What about next weekend (either Tue-Fri-Sat, or > Fri-Sat-Sun)? Would that > work for you guys? > Sure. I can set aside at least a few hours next weekend. Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 Discover Yahoo! Have fun online with music videos, cool games, IM and more. Check it out! http://discover.yahoo.com/online.html

2 1

[clc-devel] [CLC Ticket Notification] xf68config not found
by crux＠morpheus.net 09 May '05

09 May '05

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

1 0

[clc-devel] [CLC Ticket Notification] xfce4 port should be updated,bugfix release is out
by crux＠morpheus.net 03 May '05

03 May '05

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

1 0

[clc-devel] [CLC Ticket Notification] xfce4 port should be updated,bugfix release is out
by crux＠morpheus.net 03 May '05

03 May '05

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

1 0

[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