Hi Oliver, 1. I see. Then what is the reason to publish releases on the page
https://github.com/openxpki/openxpki/releases if these releases are not workable? Looks like a very dubious adds for users. 2. As for patching for BSD, it is not a program issue but rather an organizational issue. FreeBSD ports (packages) are updated occasionally, when new release is published. Of course we can choose some special git commit which will play the role of the release. The problem is then who will name a certain git commit as a special one. Say speaking of today, which commit would you recommend as a base for FreeBSD packaging? All the best, Sergei On 17.06.2014 21:51, Oliver Welter wrote: > Hi Sergei, > > I expected Martin to jump in here as it is his area. > > Anyway, we rely on git as primary control and we also publish the git > references and tags inside the packages for better debugging and > transparency. Therefore I would encourage you to use a git checkout > instead of the tarball archive to build. If this is not doable or has > any major backdraws on BSD, please file a bug on the issue tracker with > enough details why/how you need another approach and if possible give a > hint on a solution (or directly create a patch). > > Oliver ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
