From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Manifest local ebuild - bump version
Date: Fri, 18 Dec 2020 08:35:39 +0000 [thread overview]
Message-ID: <20201218083539.73fd955b@digimed.co.uk> (raw)
In-Reply-To: <1b86b8bc-8ae6-aae1-75f1-162a30c8d78f@sys-concept.com>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
On Thu, 17 Dec 2020 23:49:28 -0700, thelma@sys-concept.com wrote:
> How bump version and manifest local ebuild.
You don't.
> I copied barcode-0.99.ebuild to local/portage and tired to bump version
> mv barcode-0.99.1.ebuild
> ebuild /usr/local/portage/app-text/barcode/barcode-0.99.1.ebuild
> manifest
>
> but when I try to manifest it, it can not find barcode-0.99.1.tar.gz (it
> doesn't exist).
Because it thinks you want a different version. You could name it 9.99-r1
but even that is not necessary.
>
> I was trying to apply this patch to current version:
> https://lists.gnu.org/archive/html/bug-barcode/2020-01/txtvoVMhO66kP.txt
Can't you just put the patch in
/etc/portage/patches/app-text/barcode/barcode-0.99 and let portage apply
it automatically when you re-emerge it?
> I can manifest (with the patch) current version: barcode-0.99.ebuild
> but renaming it after manifesting won't work, it complain about Manifest
> mismatch.
> I was trying to bump the version, so I can distinguish local from the
> official one.
>
> If I keep the version the same, how to point emerge to "local/portage".
> Do I unmerge the official one and keep the one in local/portage?
Set the priority for your overlay to be higher than portage in
repos.conf, then just re-emerge the package.
--
Neil Bothwick
COBOL: Completely Obsolete Business Oriented Language
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-18 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 6:49 [gentoo-user] Manifest local ebuild - bump version thelma
2020-12-18 8:35 ` Neil Bothwick [this message]
2020-12-18 19:00 ` Jack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201218083539.73fd955b@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox