How do I update an existing ebuild to a new version?

4761 · n00b Joined: 08 Mar 2023 Posts: 54

Hey folks,
I've really wanted to contribute to Gentoo for a while now.
I have ocassionally fixed some errors in the handbook when I noticed them, but I now wanted to start with helping maintain some packages.

So far, I'd like to just keep some outdated packages that I'd like to use up-to-date, as that's likely the best way to get into it.
I read through the Gentoo ebuild for beginners wiki, but know still very little about how ebuilds work.

So I wanted to do some hands-on maintaining by updating the mail-client/aerc package, that currently sits at version 0.16, while 0.17 is available upstream.
I figured that it wouldn't be too hard, since I'd only need to update 1 or two dependencies and bump the version number. However, the ebuild contains this line:

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2366

bstaletic · Guru Joined: 05 Apr 2014 Posts: 354

I don't know how much you actually know, so won't assume anything.
${P} is the name and version of the package. In case of sys-libs/glibc-2.39-r1, that would be glibc-2.39.

If you look at the repo structure, you will see root/${CATEGORY}/${PN}-${PV}-${PR}.ebuild
You can check all of these fancy variables in man 5 ebuild

Keeping a package up-to-date can just be renaming the ebuild file. There's also man 1 ebump from gentoolkit.
In your case, the source tarball is hosted by gentoo and you can not upload it in the name of williamh. As far as I know, your only option is to open a bug report asking for an update.

Well... alternatively, rewrite the ebuild in your local overlay, so that it uses upstream tarballs (if any), so that you can test the new version before submitting the above bug report.

NeddySeagoon · Posted: Tue Apr 02, 2024 11:43 am Post subject:

4761,

/var/db/repos/gentoo/mail-client/aerc/metadata.xml says

4761 · n00b Joined: 08 Mar 2023 Posts: 54

Thank you guys for your response!
I wasn't aware that the tarball contained the Go dependencies - new thing learned.

Neddy, is emailing the maintainer the standard approach in a situation like this, or should I file a bug report?
Thanks again.
_________________
~4761

Genone · Posted: Tue Apr 02, 2024 2:14 pm Post subject:

Filing bugs is the better approach as then there is a track record, and if the maintainer for some reason can't handle it or goes missing someone else can pick things up.

Hu · Administrator Joined: 06 Mar 2007 Posts: 22578

NeddySeagoon · Posted: Tue Apr 02, 2024 2:33 pm Post subject:

4761,

File a bug. Then its public and others will see your request and offer to help.
That will be useful even if the package you would like to start with is beyond your current skill level.
Others will see it too.

An email to the maintainer will only be seen by that one person.

I understand that go packages are jumping in at the deep end, not that there is anything wrong with that. I don't do code, so that's not a personal opinion.
You may find it easier to get started by bumping maintainer needed packages (search bugs) for other things that interest you, then filing pull requests on gitub.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

4761 · n00b Joined: 08 Mar 2023 Posts: 54

NeddySeagoon · Posted: Tue Apr 02, 2024 7:25 pm Post subject:

4761,

A request to add a new package should be a bug.
If you want to contribute the ebuild and maintain it, even better.
The guru ovorlay may be a better place to start for that.
Its developer/trusted user curated and has a lower bar to entry than ::gentoo itself.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.