[EMAIL PROTECTED] wrote:
I guess it all comes down to how "add-on" is distinguished from "standard"1. With Debian, this distinction is rather non-existant. A package is either installed or not, and this decision is done on a per-machine basis, not per-distribution.
...
I can see that Debian has a different philosophy then what I'm used to with Red Hat and Slackware. How interesting. Does this mean that producing a Debian package means placing it in some "standard" site (much as Perl's CPAN) where it becomes available to other Debian users? (It's clear I don't grasp the difference between a Debian package and an RPM package.)
Doesn't existance of a Debian package for Unicon imply that it becomes standard (read: available) in Debian? As such, it is no longer "local".
... Dunno. That's certainly not true under Red Hat, for example, where existance of an "RPM" package does not make it standard. But it sounds as though the concept of a distribution isn't as blurred there as it is with Debian. I'm sure you understand Debian better than I!
...
You can check them out independently from the Debian stuff. Its called nico (a pre-processor for Icon) and CVS-able from:
:pserver:[EMAIL PROTECTED]:/cvs co projects/PUBLIC/nico (pass=unicon)
Thanks! I'll probably try to grab a copy early next week.
-- Steve Wampler -- [EMAIL PROTECTED] The gods that smiled on your birth are now laughing out loud.
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Unicon-group mailing list Unicon-group@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unicon-group
