oddly,
@oddly@toot.re avatar

question; what is the best way to share a small improvement on an ebuild in the Guru repo? Asking to become a contributor sounds like overkill, with getting PGP working and all.

Would it be best to just create my own repo and add it to the list so it can be discovered?

@gentoo

(The improvement is making iio-sensor-proxy work on openRC by implementing a fix I found on the forums. Not that impressive, though now my Chromebook runs perfectly :))

mid_kid,
@mid_kid@fosstodon.org avatar

@oddly pull requests work, but it's not difficult to just ask for commit access either.

ferki,
@ferki@fosstodon.org avatar

@mid_kid @oddly Yep, GitHub pull requests may work, and the official bugzilla has a dedicated GURU product to collect issues:

https://bugs.gentoo.org/enter_bug.cgi?product=GURU&format=guided

In other words, it's possible to open tickets as usual, including ones with proposed patches.

Happy hacking!

oddly,
@oddly@toot.re avatar

@ferki thanks! I'm going to tinker with this over the weekend.

ferki,
@ferki@fosstodon.org avatar

@oddly Sounds great!

Thinking more about it, bugzilla may work a lot better for sending patches because:

  • the gentoo/guru repo on GitHub is only a mirror of the real repo, so merging pull requests there won't work directly
  • even if that would work, GURU maintainers in general don't have permissions to merge stuff inside the gentoo organization on GitHub

At the same time, bugzilla tickets are assigned directly to the maintainer of the ebuild in question.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • gentoo
  • everett
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • osvaldo12
  • Youngstown
  • tacticalgear
  • GTA5RPClips
  • slotface
  • rosin
  • Leos
  • kavyap
  • thenastyranch
  • khanakhh
  • JUstTest
  • mdbf
  • Durango
  • ethstaker
  • modclub
  • ngwrru68w68
  • anitta
  • tester
  • cisconetworking
  • cubers
  • megavids
  • provamag3
  • normalnudes
  • lostlight
  • All magazines