[Splashy-devel] lsb functions can't be the best solution

[Vincenzo Ampolo]

As said in #splashy there are some problems with this idea:
1) is it legal to write an /etc/lsb-base-logging.sh?
2) is this "way" flexible?

let me answer to these questions:

1) In the debian policy manual at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s7.5.1
there is written that "Firstly, as mentioned before, it is usually an
error for a package to contain files which are on the system in another
package."
To be sure i asked to the #ubuntu-motu channel:
<Goshawk> hi, this is a package creation question about the ubuntu
policy: is it legal that a package replaces or changes a configuration
file of another package?
<crimsun> Ubuntu follows Debian policy, meaning that's illegal.
<crimsun> what you _can_ do is invoke a conffile manager provided by
that other package
I don't know if the lsb-base (usually it
provides /etc/lsb-base-logging.sh) has a conffile manager and IMHO it's
not good to change a file of that package, because the version provided
by splashy can break other services.

2)IMHO, This "way" to change splashy-init (that seems mandatory due to
CPU usage and script complexity) because we can do just this:
when a script runs it calls splashy update.
But how do we recognize which script was run? it seems that, in this
way, it can be difficult to do that.
Why do i think that? easy. I'm thinking about animations (do you
remember? it was for splashy 0.3 when splashy 0.1.5 was released, maybe
now it's delayed) that in this way they can't work.

The idea showed by Otavio is better for me:
Create a new executable that talks with splashyServer, called
SplashyClient, that substitutes splashy_pgrep, splashy_update and all
these "little" programs.
In this way a simple init script will load splashyServer and
splashyClient, then SplashyClient can talk with splashyServer (but also
any other application can talk with splashyServer with unix sockets)
This way is more flexible for me. it will be more easy to implement
animations and it will be possible to control better what init is doing.

nb: just to put my feet on the ground, i started a simple C program that
already knows how to navigate into the filesystem. it can know how many
files are there in a directory and what are their names. next step is to
implement a "pgrep -n"-like function...

vincenzo at skyHome:~/Desktop$ ./a.out
starting
Number of files = 30
S01mountvirtfs S01readahead S02hostname.sh S05keymap.sh
S07linux-restricted-modules-common S08loopback S10udev S11mountdevsubfs
S13pcmciautils S15module-init-tools S17procps.sh S20checkroot.sh S22mtab
S25brltty S25mdadm-raid S26lvm S27evms S30checkfs.sh S35mountall.sh
S39readahead-desktop S40networking S40pcmcia S45waitnfs.sh S50hwclock.sh
S55dns-clean S55pppd-dns S70screen S80bootmisc.sh S85urandom
S90console-screen.sh


Thanks for your attentions...
-- 
Vincenzo Ampolo
http://www.nanofreesoft.org
http://vincenzoampolo.nanofreesoft.org
http://idp.nanofreesoft.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20060818/06b97840/attachment.pgp