Your message dated Sun, 25 Apr 2010 22:44:41 -0700
with message-id <[email protected]>
and subject line ion3 abandoned upstream
has caused the Debian Bug report #358177,
regarding More convenient default Ion3 scripts in /etc/X11/ion3/
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
358177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358177
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ion3
Version: 20060305-2
Severity: wishlist
It has somewhat irked me that deviations from the /etc/X11/ion3/ scripts
are not easily mixed in. Instead, the users have to copy the scripts to
their ~/.ion3/ and make changes there. Then Ion3 will default to
scripts in ~/.ion3/ and completely ignore files with the same name in
/etc/X11/ion3/.
The reason I get irked is that any changes to /etc/X11/ion3/ don't roll
down to end-users that have done this copying procedure. Their
versions are frozen with the copying. What I propose is that users are
able to define some booleans in a file, say ~/.ion3/defaults.lua, like
"disable_mod_dock=true". I'd use negative logic because then in the
scripts it would be easy to fit lines with conditionals to check to see
if the user would like to mix in deviations. This doesn't have to be
done for every little thing. Some Lua code can be easily undone by
custom scripts loaded later in the startup process (like selection of a
"big" F12 menu system instead of the default "query" menu system that
Ion3 now uses. However, I'm not sure everything can be so easily
undone. For instance, I don't know how to unload modules.
This might involve a little more maintenance on the part of the
developer and package maintainer, but I think it's the right way to go.
Lua certainly isn't hugely difficult to pick up, but it doesn't seem
like a bad idea to emulate conventional configuration file formats where
possible.
One of the reasons I think there's been resistance to this kind of
feature is because Ion3 users are generally motivated to keep
well-informed of new features in Ion3, and have a firm grasp of
configuration with Lua. But I'm not sure I agree with just using this
as a justification to keep things as they are. Ultimately, I'd like
Ion3 to be convenient for not only myself, but new users too.
- Sukant
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (90, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-hole
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages ion3 depends on:
ii libc6 2.3.6-3 GNU C Library: Shared libraries an
ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library
ii liblua50 5.0.2-5.1 Main interpreter library for the L
ii liblualib50 5.0.2-5.1 Extension library for the Lua 5.0
ii libsm6 6.9.0.dfsg.1-4 X Window System Session Management
ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li
ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte
ii libxinerama1 6.9.0.dfsg.1-4 X Window System multi-head display
Versions of packages ion3 recommends:
ii xfonts-100dpi 6.9.0.dfsg.1-4 100 dpi fonts for X
ii xfonts-75dpi 6.9.0.dfsg.1-4 75 dpi fonts for X
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 20090110-3+rm
ion3 and ion3-scripts have been removed from Debian unstable because
they have been abandoned upstream.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
