Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: elektra - A key/value pair database to store software configurations https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209906 ------- Additional Comments From pertusus@xxxxxxx 2007-02-21 03:57 EST ------- (In reply to comment #8) > About the source script error: the /etc/profiles.d/ directory i have do not > contain any file (which are sh or csh - so executable by definition) which do > not have executable bit set... (if you have some example i will check) They are wrong. These are core packages that were not reviewed until recently and many had packaging issues, this will hopefully be solved soon. (you could even report those issues on the merge review tickets, though somebody already did it unless I'm wrong). > I've checked for examples in glib2 or krb5 but non of theses file remove it... > they do not use %config for one or %config(noreplace) for the other. > I think this file isn't aimed to be checked by used to define their > environnement but use the environnement that conform to the package version... > (i will check by use) > Anyway The packaging guideline should state about this question... It is a question that isn't completely agreed. My personal opinion is that scripts in /etc/init.d and /etc/profile.d shouldn't be %config at all. If I recall well, previously I did differently - and I accept other contributors view. > I plan to release cinepaint which requires oyranos which requires elektra (do > you know kafka?!) So hope it will help to do so. I will use it as a base for I think that you could submit them right now, and have oyranos depend on that ticket > oyranos packaging i also hope it will help to solve differents question open > here and to know how to fix them by the examples... Requires(postun): /sbin/ldconfig isn't needed, with %postun -p the dependency is added automatically. Otherwise - I'd like to keep the statically compiled executable, but it could be done later when elektra is used in such a way that it needs to be there for recovery. What I'd like is to have the library static package be called static-devel (or devel-static) such that the static name is kept for later use for executables. - your way to package doc is certainly better than mine because it will certainly work better with --short-circuit - about putting things not in /bin and /sbin, it's fine for me, also could be reverted if elektra is needed for recovery - Putting the include file in elektra/ subdirectory implies a change in the .pc file(s) I still haven't ssen the resulting names, to see if it isn't too much transformation and if it works. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review