From: Jack Ostroff <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Question on ebuild naming/numbering
Date: Sat, 16 Nov 2024 17:04:43 -0500 [thread overview]
Message-ID: <28995acc-18ab-476e-a6fb-6d71b2a3c7da@users.sourceforge.net> (raw)
There's been an update to the gkrellm mailing list about progress on the
gtk3 conversion. It seems much of the work is being done in a specific
git branch. If I want to create an ebuild to track that branch instead
of master, what would be an appropriate numbering of that ebuild? Just
using a different name with 9999 would work - but then those two names
would have to block each other, since I don't think they could
co-exist. Are there any examples I can look at? Just adding something
after the 9999 doesn't seem right, nor does something like 9998.
Any thoughts or suggestions?
Thanks.
next reply other threads:[~2024-11-16 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 22:04 Jack Ostroff [this message]
2024-11-16 22:33 ` [gentoo-user] Question on ebuild naming/numbering Ionen Wolkens
2024-11-16 22:51 ` 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=28995acc-18ab-476e-a6fb-6d71b2a3c7da@users.sourceforge.net \
--to=ostroffjh@users.sourceforge.net \
--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