[opensuse-buildservice] optional / recommends buildrequires - openSUSE Build Service - openSUSE Mailing Lists

newer
[opensuse-buildservice] What...

[opensuse-buildservice] optional / recommends buildrequires

older
[opensuse-buildservice] obs...

Brian K. White

6 Apr 2012 6 Apr '12

08:50

Is there a way to tell the build service to include package libfoo-devel in the build environment for a given package without making it a buildrequires in the spec? Or is there a BuildRecommends or use-if-available-but-no-error-if-not-available? -- bkw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Reply

Sign in to reply online Use email software

Show replies by date

Claudio Freire

9 Apr 9 Apr

18:38

On Fri, Apr 6, 2012 at 5:50 AM, Brian K. White wrote:

Is there a way to tell the build service to include package libfoo-devel in the build environment for a given package without making it a buildrequires in the spec?

Or is there a BuildRecommends or use-if-available-but-no-error-if-not-available?

I think you're thinking about conditional[0] requirements, but the wiki[1] says (for good reasons) that they're not recommended in OBS. [0] http://www.rpm.org/wiki/PackagerDocs/ConditionalBuilds [1] http://en.opensuse.org/openSUSE:Specfile_guidelines#Conditionals -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Reply

Sign in to reply online Use email software

Brian K. White

20:16

On 4/9/2012 2:38 PM, Claudio Freire wrote:

On Fri, Apr 6, 2012 at 5:50 AM, Brian K. White wrote:

...
Is there a way to tell the build service to include package libfoo-devel in the build environment for a given package without making it a buildrequires in the spec?

Or is there a BuildRecommends or use-if-available-but-no-error-if-not-available?

I think you're thinking about conditional[0] requirements, but the wiki[1] says (for good reasons) that they're not recommended in OBS.

[0] http://www.rpm.org/wiki/PackagerDocs/ConditionalBuilds [1] http://en.opensuse.org/openSUSE:Specfile_guidelines#Conditionals

Yeah. I think I'm ok a different way. I think I just need to make use of the branch/submit/delete process more. I want to keep a branck of several packages in my home project that have .spec options that would not be appropriate for SR back to their repective devel projects, yet I do want to SR _most_ changes back to devel. So what I should probably do is figure things out in my own branch, branch from devel into tem subproject, apply changes, SR, and use the "delete if accepted" option to delete that branch if the SR is accepted. It means having two copies of the same package branched in my home, but one copy is only temporary. The example and actual packages of the moment are, I want to SR a change to graphics:tiff that buildrequires libjbigkit but only if suse_version is greater than 12.2 (not until until after jbigkit gets accepted into Factory of course) But in my own home project I don't want that suse_version limit. Both jbigkit and tiff (with some other spec changes that _would_ be safe to SR back up to graphics) build on all my targets which is suse 10.0 to current. So in my home project I want a tiff that buildrequires libjbigkit unconditionally, because _I_ have jbigkit/libjbigkit for every oS from 10.0 to current, and tiff/libtiff builds correctly with jbig for all those same versions, and _I_ want to install libjbig and jbig-enabled libtiff on all my production boxes, which range from 10.0 to current. I just didn't like the waste of obs resources of having two full copies of all such packages* just for that tiny difference in .spec *(there are more packages than that, next comes various packages like hylafax+ , ghostpdl, ghostscript, ImageMagick, etc, that can use jbig or tiff-with-jbig) But the temp branch/sr/delete is probably a workable workflow and I guess must be what you are officially supposed to do in such situations anyway so probably isn't considered abuive of obs resources. -- bkw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Reply

Sign in to reply online Use email software

Greg Freemyer

20:29

On Mon, Apr 9, 2012 at 4:16 PM, Brian K. White wrote:

On 4/9/2012 2:38 PM, Claudio Freire wrote:

...
On Fri, Apr 6, 2012 at 5:50 AM, Brian K. White wrote:

...
Is there a way to tell the build service to include package libfoo-devel in the build environment for a given package without making it a buildrequires in the spec?

Or is there a BuildRecommends or use-if-available-but-no-error-if-not-available?

I think you're thinking about conditional[0] requirements, but the wiki[1] says (for good reasons) that they're not recommended in OBS.

[0] http://www.rpm.org/wiki/PackagerDocs/ConditionalBuilds [1] http://en.opensuse.org/openSUSE:Specfile_guidelines#Conditionals

Yeah.

I think I'm ok a different way. I think I just need to make use of the branch/submit/delete process more.

I want to keep a branck of several packages in my home project that have .spec options that would not be appropriate for SR back to their repective devel projects, yet I do want to SR _most_ changes back to devel. So what I should probably do is figure things out in my own branch, branch from devel into tem subproject, apply changes, SR, and use the "delete if accepted" option to delete that branch if the SR is accepted.

It means having two copies of the same package branched in my home, but one copy is only temporary.

The example and actual packages of the moment are, I want to SR a change to graphics:tiff that buildrequires libjbigkit but only if suse_version is greater than 12.2 (not until until after jbigkit gets accepted into Factory of course)

But in my own home project I don't want that suse_version limit. Both jbigkit and tiff (with some other spec changes that _would_ be safe to SR back up to graphics) build on all my targets which is suse 10.0 to current. So in my home project I want a tiff that buildrequires libjbigkit unconditionally, because _I_ have jbigkit/libjbigkit for every oS from 10.0 to current, and tiff/libtiff builds correctly with jbig for all those same versions, and _I_ want to install libjbig and jbig-enabled libtiff on all my production boxes, which range from 10.0 to current.

I just didn't like the waste of obs resources of having two full copies of all such packages* just for that tiny difference in .spec

*(there are more packages than that, next comes various packages like hylafax+ , ghostpdl, ghostscript, ImageMagick, etc, that can use jbig or tiff-with-jbig)

But the temp branch/sr/delete is probably a workable workflow and I guess must be what you are officially supposed to do in such situations anyway so probably isn't considered abuive of obs resources.

Brian, In that case I would try to branch the graphics:tiff project to my local home project (or sub-project). Then do a osc linkpak of that branched package to "tiff-local" in your home project / sub-project. Then copy the official tiff.spec to tiff-local.spec Then edit the local spec file. That way, the first branched copy will use tiff.spec to build. The linked package will use tiff-local.spec to build. (The specfile name comes from the package name with .spec appended.) Anything you checkin to the branched package will go directly into both linked packages. What I don't know is what happens if you SR the branched package back to the devel package. Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Reply

Sign in to reply online Use email software

Dmitriy Perlow

11 May 11 May

15:34

New subject: [opensuse-buildservice] openSUSE Build Service > Projects > network > Requests

Could anybody check https://build.opensuse.org/request/show/115999 please? It was created 11 days ago. -- Dmitriy DarkneSS Perlow / Linux x64 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Reply

Sign in to reply online Use email software

Dmitriy Perlow

18 May 18 May

20:13

New subject: [opensuse-buildservice] Submit network / libqxmpp-lc to openSUSE:Factory / libqxmpp-lc

Hello to all! Could anybody check it please? https://build.opensuse.org/request/show/121072 -- Dmitriy DarkneSS Perlow / Linux x64 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Reply

Sign in to reply online Use email software

Andreas Jaeger

20:16

New subject: [opensuse-buildservice] Submit network / libqxmpp-lc to openSUSE:Factory / libqxmpp-lc

On 05/18/2012 10:13 PM, Dmitriy Perlow wrote:

Hello to all! Could anybody check it please? https://build.opensuse.org/request/show/121072

This a new package, isn't it? It's waiting for legal review and that takes a couple of days... It will be handled eventually, no worries, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Reply

Sign in to reply online Use email software

Dmitriy Perlow

20:28

New subject: [opensuse-buildservice] Submit network / libqxmpp-lc to openSUSE:Factory / libqxmpp-lc

Andreas Jaeger писал(а) в своём письме Fri, 18 May 2012 23:16:32 +0300:

On 05/18/2012 10:13 PM, Dmitriy Perlow wrote:

...
Hello to all! Could anybody check it please? https://build.opensuse.org/request/show/121072

This a new package, isn't it? It's waiting for legal review and that takes a couple of days...

It will be handled eventually, no worries,

Andreas

Thank you. It requires a review by network maintainer, doesn't it? -- Dmitriy DarkneSS Perlow / Linux x64 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Reply

Sign in to reply online Use email software

Adrian Schröter

19 May 19 May

13:16

New subject: [opensuse-buildservice] Submit network / libqxmpp-lc to openSUSE:Factory / libqxmpp-lc

Am Freitag, 18. Mai 2012, 23:28:42 schrieb Dmitriy Perlow:

Andreas Jaeger писал(а) в своём письме Fri, 18 May 2012 23:16:32 +0300:

...
On 05/18/2012 10:13 PM, Dmitriy Perlow wrote:

...
Hello to all! Could anybody check it please? https://build.opensuse.org/request/show/121072

This a new package, isn't it? It's waiting for legal review and that takes a couple of days...

It will be handled eventually, no worries,

Andreas

Thank you. It requires a review by network maintainer, doesn't it?

Yes -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Reply

Sign in to reply online Use email software

4361

Age (days ago)

4404

Last active (days ago)

Download

8 comments

6 participants

tags

participants (6)

Adrian Schröter
Andreas Jaeger
Brian K. White
Claudio Freire
Dmitriy Perlow
Greg Freemyer