[lsb-discuss] Question of LSB DDK for printing

Tatsuya Saito saitou-t at mxd.nes.nec.co.jp
Wed Mar 5 15:50:10 PST 2008


Till-san,

> > I think we may need a policy of the way to call executable modules,
> > changing path environment or using absolute path, or more 
> way if you have.
> 
> This we should really do in LSB 4.0.
I think so.

Thanks a lot for you help :)


> -----Original Message-----
> From: Till Kamppeter [mailto:till.kamppeter at gmail.com] 
> Sent: Thursday, March 06, 2008 12:08 AM
> To: Tatsuya Saito
> Cc: lsb-discuss at lists.linux-foundation.org
> Subject: Re: Question of LSB DDK for printing
> 
> Tatsuya Saito wrote:
> >> I think it makes more sense if "filternames" definition also 
> >> applies to 
> >> the "*cupsFilter: ..." entries. Please try the attached 
> >> rpmmacros file. 
> >> It will also apply the path additions defined by 
> "filternames" to the 
> >> "*cupsFilter: ..." entries of the PPD files.
> >>
> >> If it works for you please tell me and I will upload the file.
> > Thank you for updating rpmmacros.
> > I tried it and confirmed it replaced "*cupsfilter" path by 
> absolute path
> > defined "filternames".
> > I have no problem on my case, defining absolute path in 
> filternames :)
> > 
> > But it adds "/opt/splix/bin/" directory to "*cupsfilter" if 
> somebody define
> >  only filename in "filternames" like
> >  %define filternames rastertospl2
> > Because you changed code on related FoomaticRIPCommandLine.
> > I think it has to add "/opt/splix/cups/lib/filter" in ppd.
> >
> 
> To get /opt/splix/cups/lib/filter added to the use the full path in 
> "%define filternames ...":
> 
> %define filternames /opt/splix/cups/lib/filter/rastertospl2
> 
> A "%define filternames" directive without path always defaults to the 
> executable directory (/opt/splix/bin).
> 
> >> Which source file do you mean?
> > OPVP driver of IPC extention type.
> > It needs to load module and stream data such as following.
> > When they call next module, they use module name in these 
> source file.
> >  cupsfilter -> gs -> opvp ipc client library
> > -> opvp ipc server executable module -> opvp driver
> > 
> 
> [...]
> 
> >> *FoomaticRIPCommandLine: "export 
> >> LD_LIBRARY_PATH=/opt/nec/lib/; gs ..."
> >>
> >> I could also add a macro for doing this with the PPD files.
> > Some drivers/filters executable path is NOT in the PPD file.
> > For example, path of opvp ipc server executable module is written in
> > Makefile.am of opvp ipc source.
> > Of course, it differs from one case to the next.
> > 
> 
> You can use "%define filternames ..." to make the paths to the OPVP 
> driver executable appear in the PPD.
> 
> > I think we may need a policy of the way to call executable modules,
> > changing path environment or using absolute path, or more 
> way if you have.
> 
> This we should really do in LSB 4.0.
> 
>     Till

---------------------------
 Tatsuya Saito
 NEC Soft,Ltd.




More information about the lsb-discuss mailing list