unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / Atom feed
* Packaging question: Backport patch or use newer commit?
@ 2020-09-12 16:04 Zhu Zihao
  2020-09-12 16:35 ` Leo Famulari
  0 siblings, 1 reply; 3+ messages in thread
From: Zhu Zihao @ 2020-09-12 16:04 UTC (permalink / raw)
  To: guix-devel

[-- Attachment #1: Type: text/plain, Size: 563 bytes --]

Hi everybody. I' m packaging digikam(https://digikam.org). A free photo management software from KDE project. There're 2 dependecies missing from current Guix(qtav & libksane)


I tried to package qtav(https://github.com/wang-bin/QtAV/) first, but it's latest release(v1.13.0) failed to build with Qt 5.14. And it was fixed in https://github.com/wang-bin/QtAV/commit/5abba7f0505e75fc. The question is: "Should I backport this fix to v1.13.0 or just use this commit to build qtav?"


If there're some guidelines on this, please tell me, thanks a lot!


--


Zihao

[-- Attachment #2: Type: text/html, Size: 1264 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Packaging question: Backport patch or use newer commit?
  2020-09-12 16:04 Packaging question: Backport patch or use newer commit? Zhu Zihao
@ 2020-09-12 16:35 ` Leo Famulari
  2020-09-13  4:20   ` Zhu Zihao
  0 siblings, 1 reply; 3+ messages in thread
From: Leo Famulari @ 2020-09-12 16:35 UTC (permalink / raw)
  To: Zhu Zihao; +Cc: guix-devel

On Sun, Sep 13, 2020 at 12:04:11AM +0800, Zhu Zihao wrote:
> Hi everybody. I' m packaging digikam(https://digikam.org). A free photo management software from KDE project. There're 2 dependecies missing from current Guix(qtav & libksane)
> 
> 
> I tried to package qtav(https://github.com/wang-bin/QtAV/) first, but it's latest release(v1.13.0) failed to build with Qt 5.14. And it was fixed in https://github.com/wang-bin/QtAV/commit/5abba7f0505e75fc. The question is: "Should I backport this fix to v1.13.0 or just use this commit to build qtav?"
> 
> 
> If there're some guidelines on this, please tell me, thanks a lot!

In general, we try to only package what upstream considers the "latest
release".

If the latest release doesn't work, we try to fix it in the smallest way
that we can.

So, in this case, that would mean trying to apply the patch you
mentioned to the 1.13.0 release. If that works, great.

Otherwise, we have to also consider the value of our own time, and it
might be best to build the software based on the commit itself.

Does that help?


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re:Re: Packaging question: Backport patch or use newer commit?
  2020-09-12 16:35 ` Leo Famulari
@ 2020-09-13  4:20   ` Zhu Zihao
  0 siblings, 0 replies; 3+ messages in thread
From: Zhu Zihao @ 2020-09-13  4:20 UTC (permalink / raw)
  To: Leo Famulari; +Cc: guix-devel

[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]

Thanks for your help! I back port that patch and build succesfully now. That patch is small enough so I sure it's suitable for backport.





















At 2020-09-13 00:35:10, "Leo Famulari" <leo@famulari.name> wrote:
>On Sun, Sep 13, 2020 at 12:04:11AM +0800, Zhu Zihao wrote:
>> Hi everybody. I' m packaging digikam(https://digikam.org). A free photo management software from KDE project. There're 2 dependecies missing from current Guix(qtav & libksane)
>> 
>> 
>> I tried to package qtav(https://github.com/wang-bin/QtAV/) first, but it's latest release(v1.13.0) failed to build with Qt 5.14. And it was fixed in https://github.com/wang-bin/QtAV/commit/5abba7f0505e75fc. The question is: "Should I backport this fix to v1.13.0 or just use this commit to build qtav?"
>> 
>> 
>> If there're some guidelines on this, please tell me, thanks a lot!
>
>In general, we try to only package what upstream considers the "latest
>release".
>
>If the latest release doesn't work, we try to fix it in the smallest way
>that we can.
>
>So, in this case, that would mean trying to apply the patch you
>mentioned to the 1.13.0 release. If that works, great.
>
>Otherwise, we have to also consider the value of our own time, and it
>might be best to build the software based on the commit itself.
>
>Does that help?

[-- Attachment #2: Type: text/html, Size: 1801 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-09-13  4:21 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-12 16:04 Packaging question: Backport patch or use newer commit? Zhu Zihao
2020-09-12 16:35 ` Leo Famulari
2020-09-13  4:20   ` Zhu Zihao

unofficial mirror of guix-devel@gnu.org 

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://yhetil.org/guix-devel/0 guix-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-devel guix-devel/ https://yhetil.org/guix-devel \
		guix-devel@gnu.org
	public-inbox-index guix-devel

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.devel
	nntp://news.gmane.io/gmane.comp.gnu.guix.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git