Stefan Monnier (12020-07-28): > The fact that you sometimes can, seems a clear indication that the > underlying design still makes it possible: you just need a bit of code > somewhere in SANE so you can specify this URL in a more central place > than on the command line. IOW, a trivial new feature. > You're free to do so, but usually "design mistake" refers to a problem > whose consequences can only be addressed properly by a redesign, which > implies a significant rework of the code. "Significant" is a subjective threshold. Probing is less reliable than configuration: relying on probing first is a mistake. Call it design or not if you will. > I don't see why: first, AFAICT it is still fully functional without > CUPS, Not for GUI applications that do not let set an arbitrary URL. > Maybe if you write a patch and submit it along with your > bug-report/feature-request there's more chance it will? It completely depends on the mindset of the project, I am waiting to get a feel of it. Some projects have a patch welcome attitude, some do not. More importantly, some project have the attitude "I do not need this, but if you think you do, and your patch is clean and does not make the rest of the code more complex, then ok", while others have the attitude "I do not need this, therefore nobody does" and would reject the patch. If the patch is to be rejected, or just ignored, then my time would be better invested in an external work-around, it would be less effort than forking, and more convenient. Regards, -- Nicolas George
Attachment:
signature.asc
Description: PGP signature