HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] Error when running faxqclean /usr/sbin/faxqclean: relocation error: /usr/sbin/faxqclean: undefined symbol: _6faxApp.quote



David Guthu wrote:

Hopefully without upsetting the careful balance of the universe could I
inquire why features like this haven't been added to the main hylafax
distribution yet?



I haven't committed them to the hylafax.org CVS repository because they really haven't been given enough exposure yet.


I need a place where I can develop work, put it in place (commit it), and then move on without much ado. The way that things are done at hylafax.org (call it politics if you will) often don't permit me to do this due to the demands for "pretty code", "stability", "consistency", and "portability". (Although I do expect the sub-releases to be stable, consistent, and portable - the releases there just don't undergo the process that they do at hylafax.org to acheive the same.) So in the past I've had a local code repository, and I used that, and I distributed code from it as people requested it of me... and I upstreamed the patches once I felt like it was time to move them there. I would expect that most developers have their own local code repository... at least while they're developing some patch... and then they use that code themselves until it is committed and available in some "public" kind of release.

So, right now, basically the stuff at sourceforge is the public extension of what used to be my local repository. As soon as I develop something I commit it and move on. If there are problems that arise due to the development then I fix the problems rather than ripping out prior work.

Things just don't work that way at hylafax.org, and so I couldn't use the hylafax.org CVS repository. I tried. Beginning with what later became 4.2.0 I tried to do it, and now we have extended resolutions and Class 1 ECM and MMR support and JBIG support and color fax support and fax batching support, but those of us that have been around long enough should have seen how much resistence to change there is and continues to be. You'll see that in the 4.2.0 vs 4.1.9 branch/fork. You'll see that in discussions about fax batching. You'll see that in discussions about release schedules. You'll see it in other places. It was frustrating. It was discouraging.

So I moved my code repository public so that it could get more exposure than I could get it locally and so that it would be more easily-accessible to those people, like you, that needed to use leading-edge features. I've really enjoyed using sourceforge.net, and I invite others to participate. And for any who wish to help develop leading-edge features without the resistence found at hylafax.org, then I welcome that participation.

So, consequently, the code at sourceforge is always going to have more features and contain newer developments than the stuff at hylafax.org. The developments that are there will work their way in to the repository at hylafax.org, but only when they've had sufficient exposure.

Certainly this data would be useful to anyone using Hylafax in an enterprise
environment.



You know, this is what I think, too.


Thanks,

Lee.

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*




Project hosted by iFAX Solutions