[opensuse-buildservice] Projects with subdirectories
Hi, I'm a newb to the build service and am trying to add a project with subdirectories. The files in the main directory of the project added without problems (none that I didn't work through) but when I try to add files from the subdirectory (QcjData) I get the error: error: "QcjData" is not an osc working copy How do I add subdirectories to my project? -joe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 13 Aug 2007, Joe Croft wrote:
I'm a newb to the build service and am trying to add a project with subdirectories. The files in the main directory of the project added without problems (none that I didn't work through) but when I try to add files from the subdirectory (QcjData) I get the error:
error: "QcjData" is not an osc working copy
How do I add subdirectories to my project?
I think you can't. You can create another project e.g. I created home:dstoecker:perl as a "subdirectory" to my home:dstoecker, but that has some disadvantages, e.g. you can't delete it, when no longer needed (and the OBS people seem to be uable to do so as well - maybe that side blow helps :-). I would recommend you to try without subproject first, except you have really lots of packages to handle. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-08-13 09:30:45 -0400, Joe Croft wrote:
I'm a newb to the build service and am trying to add a project with subdirectories. The files in the main directory of the project added without problems (none that I didn't work through) but when I try to add files from the subdirectory (QcjData) I get the error:
error: "QcjData" is not an osc working copy
How do I add subdirectories to my project?
neither rpm nor debian packaging allow subdirectories. you have to create a tar ball of the QcjData directory. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
All, This is for the source the project is built from. The rpm package will not have subdirectories. How do the other projects handle subdirectories for their source code using the opensuse build service? -joe On Monday 13 August 2007 10:11, Marcus Rueckert wrote:
On 2007-08-13 09:30:45 -0400, Joe Croft wrote:
I'm a newb to the build service and am trying to add a project with subdirectories. The files in the main directory of the project added without problems (none that I didn't work through) but when I try to add files from the subdirectory (QcjData) I get the error:
error: "QcjData" is not an osc working copy
How do I add subdirectories to my project?
neither rpm nor debian packaging allow subdirectories.
you have to create a tar ball of the QcjData directory.
darix
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Aug 13, 2007 at 10:28:11AM -0400, Joe Croft wrote:
All,
This is for the source the project is built from. The rpm package will not have subdirectories.
Where is you project, so I can have a look at its structure?
How do the other projects handle subdirectories for their source code using the opensuse build service?
The build service's top name space contains "projects", and projects contain "packages". Packages contain files. Neither of these building blocks have a notion of subdirectories anywhere. Directories are only used on your local harddisk if you check out a working copy, to represent the structure. (Behind the curtain, the build service does use directories also, but that's another story.) projects can be listed with "osc ls". package in a project can be listed with "osc ls <project>". files can be listed with "osc ls <project> <package>". Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Hi Peter, What you save about packages and projects make sense. I actually keep the source in my CM separated like that and bring them together for the build. I guess this is what I need to know. When I want to build the packages using the build service, how do I specify the packages which go into the build? Could it be that I'm just confused and all packages in a project get built in their respective directories to make a project? From the code, then can I reference the files something like "#include ../QcjData/QcjDataWidget.h"? Thanks, Joe On Tuesday 14 August 2007 04:26, Dr. Peter Poeml wrote:
On Mon, Aug 13, 2007 at 10:28:11AM -0400, Joe Croft wrote:
All,
This is for the source the project is built from. The rpm package will not have subdirectories.
Where is you project, so I can have a look at its structure?
How do the other projects handle subdirectories for their source code using the opensuse build service?
The build service's top name space contains "projects", and projects contain "packages". Packages contain files. Neither of these building blocks have a notion of subdirectories anywhere. Directories are only used on your local harddisk if you check out a working copy, to represent the structure. (Behind the curtain, the build service does use directories also, but that's another story.)
projects can be listed with "osc ls". package in a project can be listed with "osc ls <project>". files can be listed with "osc ls <project> <package>".
Peter
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 14 Aug 2007, Joe Croft wrote:
Hi Peter,
What you save about packages and projects make sense. I actually keep the source in my CM separated like that and bring them together for the build. I guess this is what I need to know. When I want to build the packages using the build service, how do I specify the packages which go into the build?
Could it be that I'm just confused and all packages in a project get built in their respective directories to make a project? From the code, then can I reference the files something like "#include ../QcjData/QcjDataWidget.h"?
Are you mixing something here? Normally you do not acces any .h or .c files in the build. Usually you have one or more .tar or.tar.gz files and a spec file. The .tar.gz contains the whole source tree including subdirectories, configure, makefiles and all that stuff. The RPM build process extracts the source tarball, calls the makefiles (or whatever is required to build the packages), calls the install parts of the makefile and afterwards joins all the files/scripts/... into a RPM. The BuildService is thus a meta-sourcecode repository, as here the tarballs containing the actual sources as well as patch files are the "source files" and the .spec files and related stuff are like the makefiles. Or did I misinterpret your text above? Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
OOOhhhhh.... I think I see now! So I submit a tarball with the source code, and a spec file with what it takes to build the code. Do I provide any other individual files such as COPYING or README or just the tarball and rpm spec? Am I the only one who missed that idea? How do I specify that I need the qt-devel version 4.x to the build the package? Does build service have all of the development packages on them by default? -joe On Tuesday 14 August 2007 08:05, Dirk Stoecker wrote:
On Tue, 14 Aug 2007, Joe Croft wrote:
Hi Peter,
What you save about packages and projects make sense. I actually keep the source in my CM separated like that and bring them together for the build. I guess this is what I need to know. When I want to build the packages using the build service, how do I specify the packages which go into the build?
Could it be that I'm just confused and all packages in a project get built in their respective directories to make a project? From the code, then can I reference the files something like "#include ../QcjData/QcjDataWidget.h"?
Are you mixing something here?
Normally you do not acces any .h or .c files in the build. Usually you have one or more .tar or.tar.gz files and a spec file. The .tar.gz contains the whole source tree including subdirectories, configure, makefiles and all that stuff.
The RPM build process extracts the source tarball, calls the makefiles (or whatever is required to build the packages), calls the install parts of the makefile and afterwards joins all the files/scripts/... into a RPM.
The BuildService is thus a meta-sourcecode repository, as here the tarballs containing the actual sources as well as patch files are the "source files" and the .spec files and related stuff are like the makefiles.
Or did I misinterpret your text above?
Ciao
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 14 August 2007 14:19:52 wrote Joe Croft:
OOOhhhhh.... I think I see now!
So I submit a tarball with the source code, and a spec file with what it takes to build the code. Do I provide any other individual files such as COPYING or README or just the tarball and rpm spec?
Am I the only one who missed that idea?
How do I specify that I need the qt-devel version 4.x to the build the package? Does build service have all of the development packages on them by default?
No, it uses the BuildRequires: lines from the spec files. Simply add a BuildRequires: libqt4-devel in your case. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
THankyou all! This is now making a lot more sense. -joe On Tuesday 14 August 2007 08:20, Adrian Schröter wrote:
On Tuesday 14 August 2007 14:19:52 wrote Joe Croft:
OOOhhhhh.... I think I see now!
So I submit a tarball with the source code, and a spec file with what it takes to build the code. Do I provide any other individual files such as COPYING or README or just the tarball and rpm spec?
Am I the only one who missed that idea?
How do I specify that I need the qt-devel version 4.x to the build the package? Does build service have all of the development packages on them by default?
No, it uses the BuildRequires: lines from the spec files.
Simply add a
BuildRequires: libqt4-devel
in your case.
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 14 Aug 2007, Joe Croft wrote:
OOOhhhhh.... I think I see now!
So I submit a tarball with the source code, and a spec file with what it takes to build the code. Do I provide any other individual files such as COPYING or README or just the tarball and rpm spec?
You can add additional files as well. This is seldom needed. Usually you have source tarballs (or zip, or ...) and patches only.
How do I specify that I need the qt-devel version 4.x to the build the package? Does build service have all of the development packages on them by default?
Have a look at a FAQ how to build RPM's. There was a link in this group today or yesterday where to look. Also look at some packages at the build service: Some easy ones from my files: http://build.opensuse.org/package/show?package=mp3gain&project=home%3Adstoecker http://build.opensuse.org/package/show?package=rnxcmp&project=home%3Adstoecker Requiring Qt version 4 devel files would be a line like BuildRequires: qt-devel >= 4.0 The Build-service has all the packages, which are available in the distributions it handles (SUSE 10.x and later, Fedore 5 and later, Mandriva 2006 and later and the .deb systems Ubuntu and Debian working a little bit different). Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (5)
-
Adrian Schröter -
Dirk Stoecker -
Dr. Peter Poeml -
Joe Croft -
Marcus Rueckert