Re: [cssed-devel] New plugin: developer doc plugin

[<mic...@ea...>]

Le 20 sept. 2004, =E0 12:21, Iago Rubio a =E9crit :
> On Mon, 2004-09-20 at 09:50, Mich=E8le Garoche wrote:
>> Le 20 sept. 2004, =E0 9:25, Iago Rubio a =E9crit :
>>>
>> Yes, I know, but this is the Fink policy. Of course I have to disable
>> what does not work at all or is not at relevant, but should patch =
what
>> is possible to run with a patch.
> Good policy, but put's lots of weight on the packager as it must code
> and fix, that's a developer task.
Yes, that's why I fear not to be able to port something. It comes from=20=

the fact the majority of maintainers are actually developers on Unix,=20
Linux, BSD or even Apple, and very good ones.

>> That's the theory, and you can be sure that if I don't make a release
>> as soon as you do one, I have mailing either in my box or directly in
>> user's/developer's mailing list complaining I don't port the new
>> release. That's Mac users, they are used to have the most updated=20
>> thing
>> quickly.
> Ask him to join the cssed-devel and scream here his complains :))
I doubt he wants and I'll get in return a bunch of imprecations. :-))))

> If you "don't know how" you cannot do it. If "it cannot be done" =
nobody
> can do it ;)
If I don't know, I have to ask other developers, other maintainers,=20
many mailing lists, forums, read a bunch of literature till I find a=20
way either to do it or to be sure it's undoable. And that's what I've=20
made for cssed. It was not at all obvious form, huge crisis of panic=20
when you announce you'd make plugins :-)

> There'll be things non portable as mmap for windows or ipc for Mac.
Yes, but there is a way to patch it so that it works, so that's what I=20=

call portable, even if I don't know exactly how to do it.

As for ipc queue, I must investigate since Apple has made changes in=20
ipc recently, not sure it is enough to support full ipc queue, but it=20
may have improved. So what was false yesterday could be true tomorrow.


> Well, lot's of people adds features to packages. As example Fedora=20
> ships
> ls with the new -Z option for NCSA/SElinux contexts.
> It's also based in the original sources ... but extended a bit.
> Meanwhile you publish your code, and document the changes, it's up to
> you to add anything to cssed.
Yes, but that's what I told you, it must be someone who makes an=20
addition as developer, here NCSA/SELinux, then Fedora can use it. So if=20=

I want to add something I've made to cssed, I have to put the addition=20=

under my name on SF for example, then I can effectively add it as a=20
plugin to cssed as maintainer this time. But I cannot simply make my=20
plugin on my disk and add it surreptitiously to cssed.  Anyway I don't=20=

like both ways, since it can lead to great discrepancy between ports.

> If a small feature is added it will be release as revision # ( mean
> 0.3.1 "adds a turtle icon to the toolbar, once clicked cssed will run
> twice slower" ;)
That, I'll add it :-)))

Mich=E8le
<http://micmacfr.homeunix.org>