Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 926284 - Add net-wireless/bluez-9999 ebuild
Summary: Add net-wireless/bluez-9999 ebuild
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Pacho Ramos
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-06 20:03 UTC by Joakim Tjernlund
Modified: 2024-03-12 10:20 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
bluez-9999 ebuild (bluez-9999.ebuild,7.66 KB, application/vnd.gentoo.ebuild)
2024-03-06 20:03 UTC, Joakim Tjernlund
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joakim Tjernlund 2024-03-06 20:03:53 UTC
Created attachment 886830 [details]
bluez-9999 ebuild

Upstream has fixed quite a bit of Gentoo patching for bluez
I updated my bluez-9999 ebuild best I could and I figured I offer it here.
Comment 1 Pacho Ramos gentoo-dev 2024-03-10 11:03:10 UTC
Sorry but I won't add neither keep updated a live ebuild. I prefer to get the fixes in the regular versions or take a snapshot if really needed
Comment 2 Joakim Tjernlund 2024-03-10 20:49:50 UTC
You don't have add a -9999 ebuild.
If you name it 5.73 it should just work.
Comment 3 Pacho Ramos gentoo-dev 2024-03-12 09:28:42 UTC
But people will expect the ebuild to work and be properly maintained, and that is hard as upstream changes the live sources often. Also, people could hit some obscure bugs only present in the snapshot of one exact day. That is a bit risky as bluez is used by many other applications, and maybe those bugs are going to indirectly affect other reverse dependencies.

The disadvantages are a bit explained at:
https://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/vcs-sources/
https://leo3418.github.io/2023/02/07/avoid-9999-only-gentoo-packages.html
Comment 4 Joakim Tjernlund 2024-03-12 10:20:52 UTC
(In reply to Pacho Ramos from comment #3)
> But people will expect the ebuild to work and be properly maintained, and
> that is hard as upstream changes the live sources often. Also, people could
> hit some obscure bugs only present in the snapshot of one exact day. That is
> a bit risky as bluez is used by many other applications, and maybe those
> bugs are going to indirectly affect other reverse dependencies.
> 
> The disadvantages are a bit explained at:
> https://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/vcs-sources/
> https://leo3418.github.io/2023/02/07/avoid-9999-only-gentoo-packages.html

I think you misunderstand somewhat. If you name the ebuild bluez-5.73.ebuild
it will do the normal download(same as the existing ebuilds) and build the
just released 5.73 version.

This ebuild is then only "prepared" for anyone that wants to try out
git builds by copying it to the -9999 name.

if you still don't like it, just delete the
if [[ ${PV} = 9999 ]]; then
		inherit git-r3
		SRC_URI=""
		EGIT_BRANCH="master"
		EGIT_REPO_URI="https://git.kernel.org/pub/scm/bluetooth/bluez.git"
fi

and you should have a working 5.73 ebuild without any git in it