Re: openarc-1.0.0.Beta0

[Sergey Ivanov <seriv@xxxxxxxxxx>]

Hi Andreas,
thanks for fixing!

I am not sure about "betterness" of the other option, that is, Fedora
COPR (which stands for "COmmunity PRojects").
I just tried it, and was able to build packages for x86_64 architecture
for Fedoras 26 - 28 and rawhide, Mageias 6 and cauldron, and OpenSUSE
leap and Tumbleweed. These are all but "generic" OSes there, but there
are different architectures.

As I understand, to be deployment-friendly, the project should have
Makefile target to make packages, like 'make pkgs' in zfsonlinux has in
it's git repo. Or it should supply in the repository not just
openarc.spec.in or openarc.spec.am, but full openarc.spec.  You see,
'./configure' is usually called from this file and inspects OS where it
is running, so why it should overwrite itself? And usually most of the
repositories I was dealing with for building packages provides
./configure too.

By the way, OpenSUSE Build service, - does it have a repository and
history? I have forked on github.com OpenARC and added openarc.spec and
made it buildable, but it is the first time I am having spaces in the
beginning of "ARC-" headers! How did you fix these?

-- 
  Regards,
  Sergey.

On 08/01/2018 04:52 PM, A. Schulze wrote:
>
> Am 01.08.2018 um 17:14 schrieb Sergey Ivanov:
>> Also I do not see any way for collaboration. I can clone the github
>> repository, but it's tag v1.0.0.Beta0 differs pretty much from the
>> sources I got from SUSE build service.
> Sergey,
>
> yes, that's an valid point.
>
> The primary reason to use the openSUSE Build Service was an easy way to produce binary packages.
> Could you suggest other/better options?
>
> Andreas
>  
>