Modified raspberrypi-vc

The builds are successful (rpmbuild and mock) but not until koji. I built the packages natively using pi. As for the koji build, I get the error

FAILED: ActionNotAllowed: policy violation (build_from_srpm)

Will check back into it to overcome the error.

Here are the link to my source rpm and the specfile.

Source rpm
Spec File

Firmware and Userland packages

As of the moment, I have successfully made 2 spec files. One is for the firmware and the other for the userland. The firmware contains just the firmware that was originally obtained from raspberrypi-vc and the userland spec file contains all the libraries from raspverrpi-vc. Here are the links to the file.

All of them was build successfully and installed.

Link -> This is the folder that contains the binaries and src rpm of both userland and firmware.

*1st things first, make sure to put the sources from specfiles to the designated SOURCES directory.

Modified raspberrypi-vc package (Links to the rpms)

These are the files that was build by the modified spec file of raspberrypi-vc. The link to the spec file is located to my previous blog.

RPM links:

SourceRPM
raspberrypi-vc-demo-source
raspberrypi-vc-firmware
raspberrypi-vc-libs
raspberrypi-vc-libs-devel
raspberrypi-vc-static
raspberrypi-vc-utils

RPMlint info

Errors were found during the rpmlint process but the error was inherited from the unmodified raspberrypi-vc package(errors were exactly the same), so I did not change anything as I want Chris' input if what I have done is correct.

Modifying raspberrypi-vc package(spec file)

My previous blog talked about making a new package the raspberrypi-userland. The process was pretty much straightforward but a lot of the files from the raspberrypi-vc package will conflict to it. So, I decided to just modify the raspberrypi-vc package as is.

Here's what I've done.

First, I got the source code of the raspberrypi-vc package from koji then get the source tarball from firmware. I ran the rpmbuild process to the specfile from koji and see what files were made. I found out that the whole building process was building the directory /opt/vc that will include the necessary libraries. On the other hand, the raspberrypi-userland I made, had the same goal, which was making the directory /opt/vc with exactly the same files from raspberrypi-vc. The only difference between the two is that the raspberrypi-userland included a build script and in a sense it was building from source while the other was not.

After finding out what both spec files build, I tried to combine the lines from raspberrypi-userland specfile to the raspberrypi-vc specfile. In this process we need the source files from firmware and userland and extract them to the BUILD folder so that the specfile will look into those directories in order to get the necessary files to build.

Now, the raspberry-vc specfile is now getting the files from the source(userland) instead of its own(firmware). In this sense, I have accomplished the goal to build the package from source. I just need Chris' input if this is the one( or the way) he wanted it to be. I hope it does.


Links to my specs.

raspberrypi-vc SPEC
raspberrypi-userland SPEC