op 30-09-13 17:30, Greg Freemyer schreef:

On Mon, Sep 30, 2013 at 10:55 AM, Daniël Huisman wrote:

...

Hi all,

I'm not sure this is the right mailing list but here I go.

After a long search on howto making packeges and a lot of try and more error I was hoping you all could help.

For a development project I have to run ccbuild, it makes dynamic makefiles. But I can't find any package to install it. I don't like building and running from source. It prevents from keeping track of what is installed.

That said I have a spec-file for ccbuild that looks okay. But it needs bobcat (Brokken's Own Base Classes And Templates). And that's where the big problem is. I can't seem to get a spec-file to build it. I always get an error on the directory or the files in use.

So I was hoping you could help me making a package for ccbuild and/or bobcat. I even think that there will be dev how would like to see them in openSUSE.

Best regarts Daniël Huisman

bobcat: http://bobcat.sourceforge.net/ made my Frans Brokken the same one as icmake ccbuild http://www.logfish.net/pr/ccbuild/ spec-file at https://build.opensuse.org/package/view_file/home:Drunken/ccbuild/ccbuild.sp... Daniel,

You're stuck at step zero.

If you click on the word "failed" at https://build.opensuse.org/package/show/home:Drunken/bobcat you get the build log including the error 3 or 4 lines from the end of the log:

error: File /home/abuild/rpmbuild/SOURCES/bobcat_3.16.00.orig.tar.gz: No such file or directory

And indeed if you look at the contents of that package, all it has is a specfile. As a general rule a package has to have a tarball (*.tar.gz or similar) to build from and a specfile to control the build process.

The specfile as it exists assumes that bobcat_3.16.00.orig.tar.gz has been added to the project. You need to either do that or add a different tarball and update the specfile with the alternate name.

Greg Hi Greg,

I know. The testing of the spec-files I did on my own computer. It builds way faster then the openbuild service so it's easier for testing. But I have added the sourcefile to the project. And bobcat gives me the same error as it does on my pc. Even writing the %setup myself didn't work. Daniël -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Mon, Sep 30, 2013 at 11:39 AM, Daniël Huisman wrote:

Hi Greg,

I know. The testing of the spec-files I did on my own computer. It builds way faster then the openbuild service so it's easier for testing. But I have added the sourcefile to the project. And bobcat gives me the same error as it does on my pc. Even writing the %setup myself didn't work.

Agreed, but when asking for help I typically push what I have to OBS so others can see what I'm doing. As Christian said, changing the Name: field from Bobcat to bobcat will get you past the first error. The next error is you need to add: BuildRequires: icmake The 3rd error is your call to build in the %install section %install %{__rm} -rf %{buildroot} ./build install DESTDIR=%{buildroot} I don't know what that is supposed to be so I'll let you chew on it. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Hi all, I have done some minor changes to enlightenment branding / theming, SR 201655 introduces a new package containing a theme that fits with the rest of openSUSE branding, SR 201657 updates the openSUSE profile to use the theme from the new package. (In enlightenment on first run the user is given a choice of several profiles, e-profile-openSUSE adds a profile tailored to openSUSE. SR 201660 updates the openSUSE enlightenment branding package to include this theme and to recommend several of our other themes (so the user can choose). I think these changes while sort of adding a new feature but sort of fixing the bug of having inconsistent branding a low impact and low risk (we still ship the upstream configuration as well). It would be great if these 3 changes could find there way into openSUSE 13.1 as that was there original target before family life got in the way, there is no point in including 201657 without 201655 and also no point in including 201660 without 201655 and 201657. If anyone is interested in what this actually looks like there are some screen shots on my blog http://simotek.net/tech/opensuse-e17-theme/ If this is the wrong place for this email or you have any criticisms of what i could do better for next time feel free to let me know, i'm still learning procedures. There was a discussion some months back with a resolution to add enlightenment to the DVD, and a radio button to the installer, is there still time to make this happen? and is there anything i can do to help the process? Cheers, Simon Lees, Enlightenment co maintainer for openSUSE #simotek on freenode. --- Links mostly for my benefit Enlightenment theme for openSUSE 13.1 https://build.opensuse.org/request/show/201655 Profile https://build.opensuse.org/request/show/201657 Branding https://build.opensuse.org/request/show/201660 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org