Hello,

elektra is finally in fedora, thanks to Nicolas Chauvet (and I), 
reviewed by Ralf - he doesn't like elektra, but the package meets
the fedora quality standards, so he approved it. I am the primary
maintainer, Nicolas is co-maintainer and Avi is in CC for the bugs.
That was one of the hardest package submissions I was involved in.
If I am not wrong Nicolas should package oyranos in fedora.

Basically there are 3 differences between the package and a 
classical install:

1. include files are in $prefix/includedir/elektra/ (not in
  $prefix/includedir/)
2. scripts, executable names, corresponding man pages and /var files or
  dirs are prefixed by elektra- 
3. statically compiled kdb and elektra library are not shipped.
4. all the libraries are in $prefix/lib, not in /lib

What to do in the spec file provided with elektra (and in elektra)?

My opinion is that
* regarding 3. we should ship the static parts in the spec, with the
  subpackages I did.

* in my opinion, 1. is right and should be done in elektra

* regarding 2. I think it should be better handled at the elektra level. 
  Many users will use the packages, and it would be much better if the 
  executables had the same name everywhere (in the docs, in main elektra
  and in the packages).

  If we don't do modify the main elektra, what should be done for the
  spec file? Do like in fedora or like in the main package?

* regarding 4. I think we could put things in / in the spec file, but
  putting things in $prefix is simpler. What do you prefer?

--
Pat
 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Registry-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/registry-list

Reply via email to