[opensuse-gnome] a simple package, documented
Hey, I just finished up the first version of http://en.opensuse.org/GNOME/Packaging/Simple_program_package , which documents a simple yet reasonably complete .spec file. Comments or fixes are welcome. BTW, I will be creating a similar page but for a GNOME library -- any suggestions for which one to use? -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
fre, 26.10.2007 kl. 14.26 -0500, skrev Michael Wolf:
Hey,
I just finished up the first version of http://en.opensuse.org/GNOME/Packaging/Simple_program_package , which documents a simple yet reasonably complete .spec file.
From your wiki:
Build requirements Here we list build requirements. This should be a minimal set of dependencies required to build the package. Note that if one package requires another, then it is only necessary to list the requiring package. For example, if your program uses functionality provided by the glib2 package and the gtk2 package (a common occurrence), then it is only necessary to explicitly list gtk2-devel, since gtk2-devel depends on glib2-devel. ---------------------- Maybe some info on how to find out deps like that? Or is that too obvious? What I'm asking here is a example of the cli-fu that is needed to find out that. I have foo.src.tar.gz. In the readme it lists requires x,y and z. x and y are deps of z, but how do I, the first time packager know this. Bjørn -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Fri, 2007-26-10 at 22:02 +0200, Bjørn Lie wrote:
Maybe some info on how to find out deps like that? Or is that too obvious? What I'm asking here is a example of the cli-fu that is needed to find out that.
I have foo.src.tar.gz. In the readme it lists requires x,y and z. x and y are deps of z, but how do I, the first time packager know this.
No, that isn't too obvious. One of the hard parts of writing documentation is that it's easy to forget or not even realize that other people don't know things that you take for granted. I'll try to improve this section of the page soon, and thanks for your feedback. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Fri, 2007-10-26 at 17:18 -0500, Michael Wolf wrote:
On Fri, 2007-26-10 at 22:02 +0200, Bjørn Lie wrote:
Maybe some info on how to find out deps like that? Or is that too obvious? What I'm asking here is a example of the cli-fu that is needed to find out that.
I have foo.src.tar.gz. In the readme it lists requires x,y and z. x and y are deps of z, but how do I, the first time packager know this.
No, that isn't too obvious.
can't we have something like whatdependson (and a counterpart onwhatdepends) like we have in autobuild? As OSC plugins they would make lots of sense
One of the hard parts of writing documentation is that it's easy to forget or not even realize that other people don't know things that you take for granted.
I'll try to improve this section of the page soon, and thanks for your feedback.
the same happens for lots of the stuff in that page, an explanation of: * %suse_version valid values and the details about them (what prefix they use, etc) * BuildRoot, Autoreqprov * %gconf_schemas_prereq That would make the page very self-explaining -- Rodrigo Moya <rodrigo@novell.com> -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Mon, 2007-29-10 at 13:45 +0100, Rodrigo Moya wrote:
On Fri, 2007-10-26 at 17:18 -0500, Michael Wolf wrote:
On Fri, 2007-26-10 at 22:02 +0200, Bjørn Lie wrote:
Maybe some info on how to find out deps like that? Or is that too obvious? What I'm asking here is a example of the cli-fu that is needed to find out that.
I have foo.src.tar.gz. In the readme it lists requires x,y and z. x and y are deps of z, but how do I, the first time packager know this.
No, that isn't too obvious.
can't we have something like whatdependson (and a counterpart onwhatdepends) like we have in autobuild? As OSC plugins they would make lots of sense
Yeah, that would be sweet. It could probably build off of or supplement the pkg-config scripts Stanislav sent last week, and a lot of the information is available through the buildservice API too.
One of the hard parts of writing documentation is that it's easy to forget or not even realize that other people don't know things that you take for granted.
I'll try to improve this section of the page soon, and thanks for your feedback.
the same happens for lots of the stuff in that page, an explanation of:
* %suse_version valid values and the details about them (what prefix they use, etc) * BuildRoot, Autoreqprov * %gconf_schemas_prereq
That would make the page very self-explaining
Good suggestions. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
participants (3)
-
Bjørn Lie -
Michael Wolf -
Rodrigo Moya