Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#23344 - [fop] /etc/fop.conf has weird content

Attached to Project: Community Packages
Opened by Andreas Baumann (andreas_baumann) - Saturday, 19 March 2011, 08:48 GMT
Last edited by Stefan Husmann (stefanhusmann) - Tuesday, 22 March 2011, 18:51 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Stefan Husmann (stefanhusmann)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



/etc/fop.conf contains:


(so it contains the CLASSPATH of the user building the package, which is not what you want)


echo \
"CLASSPATH=\"$CLASSPATH:/usr/share/java/batik/xml-apis-ext.jar\"" \
>> $pkgdir/etc/fop.conf

I don't understand why /etc/fop.conf can't be adjusted directly. On the other hand, if this entry
is needed only for 'batik' then it should be added there.

IMHO: I wouldn't have a global /etc/fop.conf, I would try to make a global /etc/fop.conf including
from /etc/fop.conf.d some config file snippets per optional fop package.

Additional info:
* package version(s)
fop 1.0-2
java-batik 1.7-8

* config and/or log files etc.

Steps to reproduce:
This task depends upon

Closed by  Stefan Husmann (stefanhusmann)
Tuesday, 22 March 2011, 18:51 GMT
Reason for closing:  Fixed
Comment by Stefan Husmann (stefanhusmann) - Sunday, 20 March 2011, 04:43 GMT
Sorry for the stupid bug. It is fixed in -3.

Regarding your suggestions: Config files are merely under control of the administrator. Packages only should provide sane defaults.

Comment by Stefan Husmann (stefanhusmann) - Tuesday, 22 March 2011, 18:51 GMT
Sorry again, I did not get your point in "I don't understand why /etc/fop.conf can't be adjusted directly. " Now I got it.