RE: [Webware-discuss] webware debian package

[Matt F. <ma...@da...>]

| /usr/share/webware/ for library modules (most of Webware).
| /usr/bin/ for wrapper scripts run from the command line (MakeAppWorkDir).
| /etc/webware/ for configuration files (edited by sysadmin).
| ~/.webware for usr-modified configuration files.

[etc]

Well, it really doesn't seem that webware works this way. It's not split out
and sprinkled all over the system, and I don't think it would be attractive
to have it work one way on Debian and one way everywhere else.

Webware should probably remain a monolithic install; one place with all of
the goods, with small exceptions like /etc/init.d/ file. I suppose one could
symlink everything, but that seems awful crufty.

It's possible (likely?) that Webware cannot be installed according to the
debian guidelines.

And about your point of an ISP... that's interesting. I know the subject has
come up. Again, though, webware doesn't seem to have traditional /etc/ file
setups... that could be overriden in a users ~/.webware directory. There is
the MakeAppWorkDir thing, but that's also sortof monolithic; just an
offshoot.

Clearly, and ISP wouldn't want each of its users to have its own appserver
with 10 python threads running.

So, we probably can't do the .deb "right", but we can maybe do it half-assed
for ourselves.

Thoughts?