I'd be *really* annoyed if command line printing went away.  I don't care if 
it's lpd or lpr, but I work mostly in text mode using a stack of xterms, one 
per work project.   So having to start up a GUI window to print  could easily 
get annoying.  I use a2ps to format stuff to feed to lp.  

On a separate subject:

WHO ADMINISTERS THE OI MAILING LISTS?  HOW CAN I CONTACT THEM?

Posting anything to the OI lists will cause me to get dropped because of 
bounces resulting from the yahoo DMARC policy.  I had Klimov post to the 
"discuss" list about this and I've emailed the list admins, but without any 
response.  The Illumos lists have fixed the problem, so it's not that difficult.



--------------------------------------------
On Tue, 5/6/14, Peter Tribble <[email protected]> wrote:

 Subject: Re: [oi-dev] [developer] 2837 - remove print/lp* from gate and use    
CUPS from userland
 To: "Garrett D'Amore" <[email protected]>
 Cc: "OpenIndiana Developer mailing list" <[email protected]>, "Developer 
Lists Illumos" <[email protected]>
 Date: Tuesday, May 6, 2014, 9:43 AM
 
 What
 part of the lp stack actually uses apache? I suspect
 it's only
 ipp, mod_ipp
 specifically, and that the rest of the lp stack
 has no dependency at all. I would be
 perfectly happy to see
 
 all the ipp stuff ripped out (I've never used
 it, and my understanding
 is that
 CUPS provides a much better implementation anyway)
 especially if it allows us to
 eradicate apache-13. However., I'm not
 
 sure that this extends to the rest of the legacy lp
 stack.
 
 The
 argument that legacy stuff could simply be dropped off to
 one
 side in a legacy repo would
 be far stronger if we actually had
 
 such a repo in place. I regard creating that
 infrastructure as a
 necessary
 prerequisite to any significant pruning of the codebase.
 
 (Although I'm
 not sure it needs a full-blown repo. Tarballs of the
 
 source that's ripped out, placed in a well-known
 location, ought
 to be adequate.)
 
 
 
 
 On Tue,
 May 6, 2014 at 3:07 PM, Garrett D'Amore <[email protected]>
 wrote:
 
 I'd love to see it go.  But I
 will wait for others to complain first.
 
 
 
 One idea would be to eject it from the gate and put it into
 a new repo where it could also be updated if people still
 want it.
 
 
 
 Sent from my iPhone
 
 
 
 > On May 6, 2014, at 12:48 AM, "Alexander
 Pyhalov" <[email protected]>
 wrote:
 
 >
 
 > Hello.
 
 >
 
 > When I tried to rebuild apache 1.3 again I found out
 that mod_ssl doesn't like OpenSSL 1.0.
 
 > Of course, I could look at it and try update it, but
 does someone really use apache 1.3?
 
 > Now it's only used as illumos-gate build
 dependency.
 
 >
 
 > Last time the question of removing print/lp* from the
 gate was rejected partially because cups didn't provide
 trusted printing support.
 
 > Our (OI /hipster) version of cups has TX patches.
 However, I haven't checked that it works.
 
 > As I understand, most distributions have already
 stripped this code. Isn't it a good time to reconsider
 the question - either update dependency to apache 2 or
 remove it?
 
 > --
 
 > Best regards,
 
 > Alexander Pyhalov,
 
 > system administrator of Computer Center of Southern
 Federal University
 
 >
 
 >
 
 > -------------------------------------------
 
 > illumos-developer
 
 > Archives: https://www.listbox.com/member/archive/182179/=now
 
 > RSS Feed: https://www.listbox.com/member/archive/rss/182179/21239177-3604570e
 
 > Modify Your Subscription: https://www.listbox.com/member/?&;
 
 > Powered by Listbox: http://www.listbox.com
 
 
 
 
 
 -------------------------------------------
 
 illumos-developer
 
 Archives: https://www.listbox.com/member/archive/182179/=now
 
 RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175229-59db2a15
 
 Modify Your Subscription: 
https://www.listbox.com/member/?member_id=21175229&id_secret=21175229-7dd7c4fa
 
 
 Powered by Listbox: http://www.listbox.com
 
 
 
 
 -- 
 -Peter Tribble
 http://www.petertribble.co.uk/
 - http://ptribble.blogspot.com/
 
 -----Inline Attachment Follows-----
 
 _______________________________________________
 oi-dev mailing list
 [email protected]
 http://openindiana.org/mailman/listinfo/oi-dev

_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev

Reply via email to