Build Service Useless Because Its too complicated

[linuxcpa]

So I just want to upload some source code from here: http://www.hampa.ch/pce/

Builds without a problem on my system

./configure
make
make install

I must have wasted hours just trying to figure out what the name of the spec file was supposed to be, changes file. OK got that.

Then I got a sample spec file.

Can't someone make the web interface make the user fill out a web page and then it will create the spec file?

There are so many **** variables - the log keeps coming back with:

error: File not found by glob: /home/abuild/rpmbuild/BUILDROOT/pce-0.2.2-47.1.x86_64/usr/bin/*

WTF am I supposed to do list every binary that builds separately in the spec? I tried that and it gets appended to BUILDROOT.

Pkgsrc is easier to use.

Spec File:

#
# spec file for package pce
#
# -- Copyright omitted --

Name: pce


Version: 0.2.2


Release: 0


License: GPL-2.0


Group: Emulation


Summary: Mac Plus / PC and Atari Emulator


Url: http://www.hampa.ch/pce/


Source: http://www.hampa.ch/pub/pce/pce-0.2.2.tar.gz


BuildRequires: gcc


BuildRequires: make


BuildRoot: %{_tmppath}/%{name}-build

%description

PCE is a collection of microcomputer emulators. At the moment it contains three emulators:

PCE/atarist is an Atari ST emulator. It emulates the various ST and Mega ST models.

PCE/ibmpc is an IBM PC 5150 emulator. It emulates an IBM PC 5150 or an IBM PC/XT 5160.

PCE/macplus is a classic Macintosh emulator. It emulates a Macintosh 128K, Macintosh 512k, Macintosh 512ke, Macintosh Plus, Macintosh SE or a Macintosh Classic.

PCE/rc759 is a Regnecentralen RC759 Piccoline emulator.

%prep


%setup -q -n %{name}-%{version}

%build



%install



%files



%defattr(-,root,root,-)
%doc README LICENSE *.txt
%{_bindir}/*

%changelog

[malcolmlewis]

Hi
The %<placeholders> require the commands like configure, make install added, so nothing is being done with your spec file except extract the source....

#
# spec file for package pce
#
# -- Copyright omitted --

Name:           pce 
Version:        0.2.2 
Release:        0 
License:        GPL-2.0 
Group:          System/Emulators/Other
Summary:        Mac Plus / PC and Atari Emulator 
Url:            http://www.hampa.ch/pce/
Source:         http://www.hampa.ch/pub/pce/pce-0.2.2.tar.gz 
BuildRequires:  gcc 
BuildRequires:  make 
BuildRoot:      %{_tmppath}/%{name}-build

%description 
PCE is a collection of microcomputer emulators. At the moment it contains three emulators:

- PCE/atarist is an Atari ST emulator. It emulates the various ST and Mega ST models.
- PCE/ibmpc is an IBM PC 5150 emulator. It emulates an IBM PC 5150 or an IBM PC/XT 5160.
- PCE/macplus is a classic Macintosh emulator. It emulates a Macintosh 128K, Macintosh
  512k, Macintosh 512ke, Macintosh Plus, Macintosh SE or a Macintosh Classic.
- PCE/rc759 is a Regnecentralen RC759 Piccoline emulator.

%prep
%setup -q -n %{name}-%{version}

%build
%configure --prefix=/usr
make %{?_smp_mflags}

%install
%make_install

%files
%defattr(-,root,root,-)
%doc README *.txt
%license LICENSE
%config(noreplace) %{_sysconfdir}/pce
%{_bindir}/aym
%{_bindir}/pce-*
%{_bindir}/pri
%{_bindir}/psi
%{_mandir}/man1/aym.1%{?ext_man}
%{_mandir}/man1/pce-atarist.1%{?ext_man}
%{_mandir}/man1/pce-dos.1%{?ext_man}
%{_mandir}/man1/pce-ibmpc.1%{?ext_man}
%{_mandir}/man1/pce-img.1%{?ext_man}
%{_mandir}/man1/pce-rc759.1%{?ext_man}
%{_mandir}/man1/pri.1%{?ext_man}
%{_mandir}/man1/psi.1%{?ext_man}
%{_datadir}/pce/

%changelog

[arvidjaar]

Can't someone make the web interface make the user fill out a web page and then it will create the spec file?

Sure. You can. This is open source, your contribution will be welcome.

WTF am I supposed to do list every binary that builds separately in the spec?

You are supposed to at least build and install them. So far you do neither.

[Fraser_Bell]

... and, you would probably get a lot of help here, if you were to ask questions in a less aggressive manner and instead a friendly question.

Lots here who can help you, if you invite them to in a welcoming manner, all of whom are volunteering and very happy to help out with something like this.

Just a tip, in a friendly tone, so you can enjoy your time here.

[dcurtisfra]

I must have wasted hours just trying to figure out what the name of the spec file was supposed to be, changes file. OK got that.
Then I got a sample spec file.
Can't someone make the web interface make the user fill out a web page and then it will create the spec file?

Assuming that, you generated a RPM spec file which meets these requirements: <http://ftp.rpm.org/max-rpm/s1-rpm-bu...spec-file.html>
you seem to be saying that, there is nothing in the OBS Wiki which indicates what the filename of that RPM spec file should be?

---

Looking through the openSUSE's OBS Wiki material and the OBS help, I tend to agree with you:

openSUSE Portal: <https://en.opensuse.org/Portal:Build_Service>
Tutorial: <https://en.opensuse.org/openSUSE:Build_Service_Tutorial>.
Tips and Tricks: <https://en.opensuse.org/openSUSE:Bui...ips_and_Tricks>.
FAQs: <https://en.opensuse.org/openSUSE:Build_Service_FAQ>.
The build configuration (details the differences between the OBS project configuration file and a RPM spec file): <https://en.opensuse.org/openSUSE:Build_Service_prjconf>.
Everything else related to OBS: <https://en.opensuse.org/Category:Build_Service>.
Manuals, Screencasts, Talks and Workshops: <https://openbuildservice.org/help/>.

---

In fact, the only hint for the name of the RPM spec file to be used, seems to be in this Lizard's Blog: <https://lizards.opensuse.org/2013/12...to-write-them/>.

---

Unfortunately, because the OBS is no longer a "free-wheeling" project, you'll need to contact the OBS maintainers to suggest the clarification you've raised.