> On Mon, 20 May 2024, Florian Schmaus wrote:
> - [[ "${PIPESTATUS[*]}" == "0 "[01]" 0" ]]
> - eend $? || die "error installing man pages"
> + [[ "${pipestatus}" == "0 "[01]" 0" ]]
Quotes around ${pipestatus} are redundant.
> +
> On Sun, 12 May 2024, Hans de Graaff wrote:
> -# @SUPPORTED_EAPIS: 7
> +# @SUPPORTED_EAPIS: 7, 8
No comma there.
signature.asc
Description: PGP signature
> On Thu, 09 May 2024, Michał Górny wrote:
>> +# it from being changed. The variable is left writable for use in overlays;
>> +# package naming restrictions would prohibit some otherwise-valid usernames.
> You're not following the original style (double spaces).
This is less about style
epatch.eclass is no longer used by any ebuild in the Gentoo repository.
(It is inherited by eutils.eclass which is itself slated for removal.)
Removal on 2024-06-08.
From 4bbeea154b6bf6a5ff93a80e83c5c8ee753c282a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulrich=20M=C3=BCller?=
Date: Wed, 8 May
> On Sun, 05 May 2024, Paul Zander wrote:
> indent_size is the width in spaces, we use tabs.
> tab_width would be the tab width in spaces, but there is no reason to
> force this.
The Devmanual says that "each tab represents four spaces" [1,2], and
ebuild-mode implements it so [3]. Maybe it
> On Sun, 05 May 2024, Paul Zander wrote:
> +# Copyright 1999-2024 Gentoo Authors
> +# Distributed under the terms of the GNU General Public License v2
No objections to a copyright header, though we probably don't need one
for a short file like this. But make it a realistic starting year
> On Fri, 03 May 2024, James Calligeros wrote:
> +Title: Potentially breaking upgrade - media-video/wireplumber-0.5.2
The title must have 50 chars as a maximum, by GLEP 42. If it is longer,
then it isn't guaranteed that eselect news will display it properly.
> +Author: James Calligeros
>
> On Fri, 03 May 2024, Sam James wrote:
> + case ${EAPI} in
> + 5|6) DEPEND=${GNUCONFIG_DEPEND} ;;
> + *) BDEPEND=${GNUCONFIG_DEPEND} ;;
> + esac
Drop EAPI 5 while at it?
signature.asc
Description: PGP signature
> On Wed, 01 May 2024, Maciej Barć wrote:
>>> Also no license link. Afaik all contribs are under GPL-2.
>> That's not entirely correct. The files in the licenses/ directory
>> aren't, and patches in packages' files/ dirs generally follow the
>> license of their upstream project.
> See, so
> On Wed, 01 May 2024, Maciej Barć wrote:
> Also no license link. Afaik all contribs are under GPL-2.
That's not entirely correct. The files in the licenses/ directory
aren't, and patches in packages' files/ dirs generally follow the
license of their upstream project.
Ulrich
signature.asc
> On Wed, 01 May 2024, Florian Schmaus wrote:
> + local grep_expressions=()
Declare f as local, too.
> + # Transform texlive_core_man_pages into grep expressions
> + # that will be used to filter out any man page that is
> +
> On Sun, 28 Apr 2024, Florian Schmaus wrote:
> --- a/eclass/texlive-common.eclass
> +++ b/eclass/texlive-common.eclass
> @@ -270,10 +270,18 @@ texlive-common_update_tlpdb() {
> touch "${new_tlpdb}" || die
>
> if [[ -d "${tlpobj}" ]]; then
> - find "${tlpobj}"
eutils.eclass is no longer used by any ebuild in the Gentoo repository.
Removal in 60 days, i.e. on 2024-06-08, so overlays will have enough
time to update.
From a1f28063e0ba2192a120d15fd82a2d59ae10c892 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulrich=20M=C3=BCller?=
Date: Mon, 8 Jan 2024
> On Sat, 06 Apr 2024, Eddie Chapman wrote:
> [...] this is ridiculous and unnecessary :-).
Indeed.
SCNR,
Ulrich
> On Tue, 02 Apr 2024, Florian Schmaus wrote:
> + # If we are updating this package, then there is no need to update
> + # the tlpdb in postrm, as it will be again updated in postinst.
> + [[ -n ${REPLACING_VERSIONS} && ${EBUILD_PHASE} == postrm ]] && return
Sorry for having
# Ulrich Müller (2024-03-06)
# Inactive upstream maintainer. Needs porting to PEP 517 (or better,
# from Python to Emacs Lisp) and from layman to repository.eselect.
# Removal on 2024-05-05. Bug #909887, #909890.
app-portage/g-sorcery
app-portage/gs-elpa
signature.asc
Description: PGP signature
>>>>> On Fri, 01 Mar 2024, Florian Schmaus wrote:
> On 29/02/2024 21.40, Ulrich Mueller wrote:
>>>>>>> On Thu, 29 Feb 2024, Florian Schmaus wrote:
>>
>>> @@ -178,6 +178,10 @@ etexmf-update() {
>>> if has_version 'app-text/texliv
> On Thu, 29 Feb 2024, Florian Schmaus wrote:
> @@ -178,6 +178,10 @@ etexmf-update() {
> if has_version 'app-text/texlive-core' ; then
> if [[ -z ${ROOT} && -x "${EPREFIX}"/usr/sbin/texmf-update ]] ;
> then
> "${EPREFIX}"/usr/sbin/texmf-update
> +
> On Thu, 29 Feb 2024, Michał Górny wrote:
>> +"${EPREFIX}"/usr/bin/fmtutil-sys --all &> /dev/null \
>> +|| die -n "fmtutil-sys returned non-zero exit
>> status ${res}"
> Put '||' at end of the line, then you won't need the redundant
>
> On Wed, 28 Feb 2024, Michał Górny wrote:
> On Tue, 2024-02-27 at 21:05 -0600, Oskari Pirhonen wrote:
>> What about cases where someone, say, doesn't have an excellent grasp of
>> English and decides to use, for example, ChatGPT to aid in writing
>> documentation/comments (not code) and puts
> On Tue, 27 Feb 2024, Rich Freeman wrote:
> On Tue, Feb 27, 2024 at 9:45 AM Michał Górny wrote:
>>
>> Given the recent spread of the "AI" bubble, I think we really need to
>> look into formally addressing the related concerns.
First of all, I fully support mgorny's proposal.
>> 1.
> On Mon, 26 Feb 2024, Andrew Nowa Ammerlaan wrote:
> Title: installkernel is no longer implicitly installed
> Author: Andrew Ammerlaan
> Posted: 2024-02-26
> Revision: 1
> News-Item-Format: 2.0
> Display-If-Installed: sys-kernel/installkernel
> Display-If-Installed:
> On Wed, 14 Feb 2024, Michał Górny wrote:
> The following packages are now looking for a new maintainer, due to
> their prior maintainer being inactive:
> sys-firmware/iwl3160-7260-bt-ucode
> sys-firmware/iwl3160-ucode
> sys-firmware/iwl7260-ucode
These should be treecleaned, because
> On Sat, 10 Feb 2024, Daniel Simionato wrote:
> I'd like to start a discussion regarding setting HOME_MODE by default in
> the /etc/login.defs file (owned by sys-apps/shadow package).
> Upstream keeps HOME_MODE commented:
>
> On Sat, 03 Feb 2024, Maciej Barć wrote:
> + find "$(pwd)" -maxdepth 1 -iname "nuget.config" -delete ||
Is there any special reason for using "$(pwd)" instead of . here?
> + case "${1}" in
Quotes not needed.
> + if [[ -d "${1}" ]] ; then
Quotes not needed.
> On Sat, 03 Feb 2024, Maciej Barć wrote:
> +dotnet-pkg_force-compat() {
> + if [[ -z "${DOTNET_PKG_COMPAT}" ]] ; then
Quotes are not needed.
> On Sat, 03 Feb 2024, Maciej Barć wrote:
> +# @FUNCTION: dotnet-pkg-base_restore_tools
> +# @USAGE: [config-file] [args] ...
> +# @DESCRIPTION:
> +# DEPRECATED, use "dotnet-pkg-base_restore_tools" instead.
Should be a hyphen here (...restore-tools), I guess?
> On Sat, 03 Feb 2024, Maciej Barć wrote:
> -if [[ ${CATEGORY}/${PN} != dev-dotnet/dotnet-runtime-nugets ]] ; then
> +if [[ "${CATEGORY}/${PN}" != dev-dotnet/dotnet-runtime-nugets ]] ; then
These quotes are not necessary.
> - if [[ ${CATEGORY}/${PN} != dev-dotnet/csharp-gentoodotnetinfo
> On Wed, 31 Jan 2024, Andreas Fink wrote:
> With the move of sys-devel/autoconf to dev-build/autoconf the ebuild
> has some inconsistency, namely in the RDEPEND section, it is saying:
> RDEPEND="
> ${BDEPEND}
>> =dev-build/autoconf-wrapper-20231224
> sys-devel/gnuconfig
>
# Ulrich Müller (2024-01-30)
# SLOT 25 of app-editors/emacs, corresponding to GNU Emacs version 25.3.
# This version was released in May 2018. Please upgrade to >=emacs-26
# and update your Emacs Lisp packages with emacs-updater.
# Removal on 2024-02-29. Bug #923329.
app-editors/emacs:25
> On Tue, 16 Jan 2024, Florian Schmaus wrote:
> case ${EAPI} in
> - 7) inherit eapi8-dosym ;;
> + 7)
> + inherit eapi8-dosym
> + dosym(){ dosym8 "$@"; }
For good reason, eapi-dosym.eclass doesn't override package manager
commands, and the texlive eclasses
>>>>> On Wed, 10 Jan 2024, Florian Schmaus wrote:
> On 10/01/2024 14.58, Ulrich Mueller wrote:
>> Looks like readme.gentoo-r1 already gives you control over this:
>> # If you want to show them always, please set FORCE_PRINT_ELOG to a non empty
>> # value
> On Wed, 10 Jan 2024, Florian Schmaus wrote:
> On 10/01/2024 12.04, Sam James wrote:
>> 1) The name seems odd (why not readme.gentoo-r2)?
>> 2) Why can't the existing eclass be improved?
> Both points, the name of the eclass and the question if this should be
> added to the existing eclass
>>>>> On Sun, 07 Jan 2024, Michał Górny wrote:
> On Sun, 2024-01-07 at 17:58 +0100, Ulrich Mueller wrote:
>> I cannot really see a delineation between app-text and [dev]-doc.
>>
>> For example, packages like psmark, xmlto, or even texi2html are general
>
>>>>> On Sun, 07 Jan 2024, Ulrich Mueller wrote:
> I cannot really see a delineation between app-text and app-doc.
Sorry, this should read "between app-text and dev-doc", of course.
signature.asc
Description: PGP signature
> On Sun, 07 Jan 2024, Michał Górny wrote:
> Here's another idea, a new dev-doc category (though I suppose we could
> try to find a better name), dedicated to:
> Tools to generate, convert, view and process documentation.
> This is notably meant to move software out of app-doc/ which is
>
>> +++
>> b/2024-01-02-separate-usr-now-requires-an-initramfs/2024-01-02-separate-usr-now-requires-an-initramfs.txt
> The short-name is rather long. [...]
In fact, the filename is also invalid by GLEP 42.
Sorry for missing this the first time.
signature.asc
Description: PGP signature
> On Tue, 02 Jan 2024, Eli Schwartz wrote:
> +++
> b/2024-01-02-separate-usr-now-requires-an-initramfs/2024-01-02-separate-usr-now-requires-an-initramfs.txt
The short-name is rather long. GLEP 42 strongly recommends to stay below
20 characters:
> On Sat, 30 Dec 2023, Andreas K Huettel wrote:
>> > we have many local gpg useflags which basically just enable gpg.
>> > Should we merge these to one global useflag?
>> >
>> > Additionally we have a few gpgme useflags.
>> > See also https://bugs.gentoo.org/679634
>> >
>> > What are your
> On Sat, 30 Dec 2023, Michał Górny wrote:
> - edob "${compress[@]}" -- "${@}"
> + edob "${compress[@]}" -- "${@}" || die
Doesn't edob already die by itself?
signature.asc
Description: PGP signature
> On Fri, 29 Dec 2023, Michał Górny wrote:
> --- a/profiles/info_vars
> +++ b/profiles/info_vars
> @@ -60,6 +60,7 @@ PORTAGE_RSYNC_EXTRA_OPTS
> PORTAGE_TMPDIR
> PORTDIR
> PORTDIR_OVERLAY
> +PYTHONPATH
> RANLIB
> READELF
> RUSTFLAGS
Please also update the copyright year in the header.
# Ulrich Müller (2023-12-26)
# Program errors out with a segmentation fault.
# Use games-fps/serioussam along with games-fps/serioussam-tfe-data
# and games-fps/serioussam-tse-data as replacement.
# Removal on 2024-01-09, bug #854567.
games-fps/serious-sam-tse
signature.asc
Description: PGP
> On Mon, 11 Dec 2023, Eli Schwartz wrote:
>> "Command-line software which adds ANSI color to its output by default
>> should check for a NO_COLOR environment variable that, when present
>> and not an empty string (regardless of its value), prevents the
>> addition of ANSI color." --
> On Mon, 11 Dec 2023, Eli Schwartz wrote:
>> +local color=yes
>> +[[ ${NO_COLOR} ]] && color=no
> [[ -v NO_COLOR ]]
No, this would give the wrong result if NO_COLOR is set to an empty
value. [[ ${NO_COLOR} ]] or [[ -n ${NO_COLOR} ]] is the correct test:
"Command-line software
> On Sun, 26 Nov 2023, Michał Górny wrote:
> 3. Forcing `NO_COLOR=1` turns out to cause random test failures,
>and while fixing them is commendable, it is a pain for arch testing
>and it is currently blocking stabilization requests.
I'd argue that test suites that fail because of
> On Sun, 22 Oct 2023, Michał Górny wrote:
> lzma - Support for LZMA (de)compression algorithm
> lz4 - Enable support for lz4 compression (as implemented in app-arch/lz4)
> +lzip - Enable support for lzip compression
Alphabetic order?
signature.asc
Description: PGP signature
> On Fri, 13 Oct 2023, Arthur Zamarin wrote:
>> Make this one either "[Bb]ugs? #\d+(,? #\d+)*" (which I'd prefer)
>> or "[Bb]ugs? +#\d+(,? +#\d+)*". That is, same number of spaces in both
>> locations.
> OK, would be hard to define it correctly in the BNF, but will just use
> {n} syntax to
> On Fri, 13 Oct 2023, Arthur Zamarin wrote:
>>> PKGS_GROUP ::= {ATOM}(\n{ATOM})*
>>
>> Sorry, I had missed this when reading it the first time. Please avoid
>> the term "atom" because neither PMS nor the Devmanual calls them so.
> Oh, sorry, normal jargon from pkgcore work. How to call
> On Fri, 13 Oct 2023, Arthur Zamarin wrote:
> PKGS_GROUP ::= {ATOM}(\n{ATOM})*
Sorry, I had missed this when reading it the first time. Please avoid
the term "atom" because neither PMS nor the Devmanual calls them so.
Ulrich
signature.asc
Description: PGP signature
> On Fri, 13 Oct 2023, Arthur Zamarin wrote:
>>> The paragraph should be of format ``Removal on ${DATE}. ${BUGS-LIST}``,
>>> where
>>> the date is RFC-3339 full-date format, meaning ``-MM-DD``, and the bugs
>>> list is of the `bugs list`_ format. The listed bugs should include the
>>>
> On Fri, 13 Oct 2023, Arthur Zamarin wrote:
> Comments Block
> --
> The comments block consists of 2 mandatory parts (`author line`_ and
> `explanation`_) and one optional part (`last-rite epilogue`_). A blank line to
> separate the parts is optional. Trailing whitespace should
> On Thu, 05 Oct 2023, Michał Górny wrote:
>> Entries Grouping
>>
>>
>> Each mask entry consists of 2 parts: `comments block`_ and `packages list`_,
>> which aren't separated by a blank line between the 2 parts. Between entries,
>> a
>> mandatory blank line must appear.
>>
> On Thu, 05 Oct 2023, Arthur Zamarin wrote:
> On 05/10/2023 06.12, Michał Górny wrote:
>> This is inconsistent with the current usage, and confusing. "After"
>> makes it unclear whether the list is inclusive (i.e. "remove on that day
>> or later") or exclusive ("remove the next day or
> On Wed, 04 Oct 2023, Arthur Zamarin wrote:
> Files can decide to add some extra file documentation, in which case, the
> entries start after the line:
> #--- END OF EXAMPLES ---
This agrees with current package.mask, but seems rather specific.
Instead of reinventing the wheel, maybe a
> On Sun, 24 Sep 2023, Jonas Stein wrote:
>> # Removal on 2023-10-21. Bug #667687, #667689.
> We should use "after" instead of "on":
> # Removal after T
I wonder if we even need to specify the wording in such detail. For any
tools parsing the file, it might be enough to say that the line
> On Sat, 23 Sep 2023, Alex Boag-Munroe wrote:
> I'm confused, you're against adding "massive header blocks" but you're
> fine with Arthur's 9 line entry but not my 8 line one.
Your 8 line entry was this (please correct me if you meant to refer to
an entry from a different message):
--- 8<
> On Fri, 22 Sep 2023, Siddhanth Rathod wrote:
> I'm writing to propose the creation of a universal remote-ID file
> within the api.git or gentoo.git in the metadata/ directory.
> Currently, we have eight different locations that require manual
> updates for any future changes, including my
> On Fri, 22 Sep 2023, Alex Boag-Munroe wrote:
> Perhaps eventually it could/should be used for the whole file but as
> an interim/beginning there's no reason you couldn't start with
> comments:
> # [PREAMBLE]
> # Timestamp: 2023-09-21 15:07:42+00:00
> # Author: Arthur Zamarin
> #
>>>>> On Fri, 22 Sep 2023, Ulrich Mueller wrote:
>>>>> On Fri, 22 Sep 2023, Florian Schmaus wrote:
>> Some, including me, consider timestamps without timezone specifiers to
>> be in local time (either of the consumer or producer of the
>> tim
> On Fri, 22 Sep 2023, Florian Schmaus wrote:
> Some, including me, consider timestamps without timezone specifiers to
> be in local time (either of the consumer or producer of the
> timestamp). Hence, if you really must have UTC here, then at least
> consider making it explicit my requiring
> On Fri, 22 Sep 2023, Oskari Pirhonen wrote:
>> Each entry is composed of 2 parts: "#"-prefixed explanation block and
>> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
>> explanation block starts (meaning first "#"-prefixed line after packages
>> list). You may add
> On Thu, 21 Sep 2023, Florian Schmaus wrote:
>> The first line of the "#"-prefixed explanation block must be of the
>> format "${AUTHOR_NAME} <${EMAIL}> (${SINGLE_DATE})" when the date is of
>> format -MM-DD, in UTC timezone.
>
> Can we drop this?
> On Thu, 21 Sep 2023, Arthur Zamarin wrote:
> = "Formal" format =
> Each entry is composed of 2 parts: "#"-prefixed explanation block and
> list of "${CATEGORY}/${PN}" packages. Entries are separated when a new
> explanation block starts (meaning first "#"-prefixed line after
> On Sun, 17 Sep 2023, Andreas K Huettel wrote:
> # Andreas K. Hüttel (2021-07-06, 2023-09-15)
Please use only a single date. The current line breaks parsing of the
date on packages.gentoo.org, which shows 0001-01-01:
https://packages.gentoo.org/packages/sys-apps/opentmpfiles
# Ulrich Müller (2023-09-20)
# Unmaintained upstream: Last release (2.92) in 2003, last commit
# to XEmacs CVS repository in 2008. Broken with Emacs 29.
# Masked for removal on 2023-10-20, bug #914449.
app-emacs/crypt++
signature.asc
Description: PGP signature
> On Sun, 17 Sep 2023, Florian Schmaus wrote:
>
>
>
> sounds perfectly fine.
Don't use an attribute if you can put the information in the (otherwise
empty) element. Especially, when other elements like already do it
that way.
> It would require (minor) adjustments to the schema and
> On Sun, 17 Sep 2023, Alexander Neuwirth wrote:
> Thanks. Instead of using the lang entry I can imagine these other
> approaches:
> 1. doi/arxiv/... links could also easily be plugged in custom upstream
> remote ids, but that also feels a bit wrong since all other [upstream
> remote
>
> On Fri, 15 Sep 2023, Alexander Neuwirth wrote:
> I am looking for a way to link scientific publications to
> ebuilds/packages. The easiest, but hacky way right now is to use the
> |https://doi.org/...|. Integration with
> |epkginfo|/|equery meta| works nicely out of the box. However,
>
> On Wed, 13 Sep 2023, Eli Schwartz wrote:
>> That's a rather bold statement. I can imagine a number of possible
>> failures, e.g. no space left on device, quota exceeded, or a low-level
>> I/O error of the filesystem. Also fork or exec of the cat command could
>> fail (e.g. out of memory).
> On Wed, 13 Sep 2023, Eli Schwartz wrote:
>> "|| die" should also be added for the cat command.
> Redirecting output to a file in a directory you have just guaranteed
> to exist cannot fail.
That's a rather bold statement. I can imagine a number of possible
failures, e.g. no space left on
> On Tue, 12 Sep 2023, Eli Schwartz wrote:
> + mkdir -p "${BUILD_DIR}" || die
> + local -x
> DIST_EXTRA_CONFIG="${BUILD_DIR}/extra-setup.cfg"
> + cat > "${DIST_EXTRA_CONFIG}" <<-EOF
> +
> On Fri, 08 Sep 2023, Michał Górny wrote:
>> > + ! has "${filename}" "${files[@]}" && continue
>>
>> This might be clearer if it was written as:
>>
>> has "${filename}" "${files[@]}" || continue
> Negative logic is never clearer.
Exactly. That's why we generally do "command ||
> On Mon, 04 Sep 2023, Michał Górny wrote:
> --- a/eclass/verify-sig.eclass
> +++ b/eclass/verify-sig.eclass
> @@ -214,12 +214,15 @@ verify-sig_verify_message() {
> }
> # @FUNCTION: verify-sig_verify_unsigned_checksums
> -# @USAGE:
> +# @USAGE:
Below,
In spite of the deprecation warning being in place for more than a year,
this seems to have caused errors with EAPI 7 ebuilds in some overlays.
Since we see some strange fixes, like downgrading of ebuilds to EAPI 6
(which is banned), here's a quick recipe for overlay maintainers how to
go for
> On Mon, 21 Aug 2023, konsolebox wrote:
> This actually allows users to virtually extend an eselect module without
> needing to fork it. The things people can do are endless.
This isn't what eselect modules were designed for. They are specialised
tools that are supposed to do one thing,
> On Mon, 21 Aug 2023, Redjard wrote:
> I did consider doing so, however with that approach my effective fork
> of the kernel.eselect module would get continually outdated, while a
> wrapper module requires a different command [...]
Not necessarily. It could use the same name as the
> On Mon, 21 Aug 2023, Redjard wrote:
> To roughly summarize, I was asking for a method to hook into eselect,
> to modify the behavior of eselect kernel set.
> I was pointed in the direction of a user patch by konsolebox, and
> consequently wrote the patch.
In addition to user patches, you
>>>>> On Sun, 23 Jul 2023, Ulrich Mueller wrote:
> I think what happens is this: sbcl is masked on musl, but it is the only
> version that is enabled in the ebuild by the IUSE="+sbcl" default.
> Therefore, none of the versions available on musl is enabled th
> On Sun, 23 Jul 2023, Andrey Grozin wrote:
> OK, sbcl is masked on musl. But why clisp, ecls, or gcl cannot be used
> in the amd64 musl profile?
> (I don't know if they actually work on amd64 musl systems, or if
> anybody ever tried to do so. I just ask a formal question about Gentoo
>
> On Sun, 23 Jul 2023, Andrey Grozin wrote:
> It seems that there are no lisps in this profile. This may be correct.
> But where are all lisps masked? I see only
> grozin@bilbo /home/gentoo/profiles $ find -name package.mask | xargs
> fgrep lisp
>
> On Fri, 21 Jul 2023, Michał Górny wrote:
> I suppose I originally didn't anticipate this many "matching" arches but
> perhaps it's time to add something like:
> arm|ppc|ppc64|riscv|sparc|sparc64)
> echo ${ARCH}
> ;;
Sounds good.
As a side note, eselect has a table with the (nearly)
> On Fri, 21 Jul 2023, Sam James wrote:
> @@ -162,6 +162,12 @@ kernel-install_get_qemu_arch() {
> ppc64)
> echo ppc64
> ;;
> + sparc)
> + echo sparc
> + ;;
> + sparc64)
>
> On Thu, 20 Jul 2023, Mike Gilbert wrote:
> On Thu, Jul 20, 2023 at 11:06 AM Florian Schmaus wrote:
>> While the bash language has no boolean datatype, you can exploit the
>> fact that 'true' and 'false' are usually shell builtins:
>>
>> : "${MESON_VERBOSE:=true}"
>>
>> and then later
>>
> On Mon, 17 Jul 2023, Mike Gilbert wrote:
> On Mon, Jul 17, 2023 at 4:27 PM Sam James wrote:
>> > Haven't we been keeping these because we still need to decide on a
>> > policy about what to do with dead acct-*/* packages?
>>
>> Right. https://bugs.gentoo.org/781881 is still open. Flow
> On Mon, 17 Jul 2023, konsolebox wrote:
>> Maybe the commit message could shortly explain why this is needed,
>> or what problem is fixed by it?
> It silences the default branch warning.
Add this sentence to the commit message then?
> If that's unwanted, kindly just close the issue.
> On Mon, 17 Jul 2023, Matt Turner wrote:
> From: konsolebox
> Closes: https://bugs.gentoo.org/841392
> Signed-off-by: Matt Turner
Maybe the commit message could shortly explain why this is needed,
or what problem is fixed by it?
signature.asc
Description: PGP signature
> On Sun, 16 Jul 2023, Arthur Zamarin wrote:
> Let me list some things as advantages to each one (since I see an
> advantage to one as disadvantage to other).
> Advantages of field in metadata.xml:
> - local to package, easier to not miss. Easier to follow for the maintainer.
> - easier to
> On Sun, 16 Jul 2023, Maciej Barć wrote:
> +case "${EAPI}" in
> + 7 | 8 )
> + :
> + ;;
> + * )
> + die "${ECLASS}: EAPI ${EAPI} unsupported."
> + ;;
> +esac
The QA team has invested quite some work to unify that case block
between
> On Fri, 14 Jul 2023, Florian Schmaus wrote:
> Posted to gentoo-dev@ since we are now entering a technical discussion
> again.
Please avoid crossposting, because that doesn't work well. (For example,
the posting will have different Reply-To headers in gentoo-project and
in gentoo-dev.)
> On Wed, 12 Jul 2023, Michał Górny wrote:
> + if [[ ${_CARGO_ECLASS} ]]; then
> + filter-lto
> + fi
Testing for an internal variable of another eclass seems less than
ideal. How about "has cargo ${INHERITED}" instead?
Ulrich
signature.asc
Description: PGP signature
> On Tue, 11 Jul 2023, Andrey Grozin wrote:
> Can somebody please edit the fricas-1.3.9.ebuild - replace the SRC_URI
> by .../${P}-full.tar.bz2 and commit it to the tree?
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4c6412ecf83a0465531c65b115b0e3ff8d875296
signature.asc
> On Tue, 11 Jul 2023, Joonas Niilola wrote:
> it would be better than the current situation for sure, but my
> impression with myspell* packages is that they all have different
> version releases and different upstream source uris, so just wondering
> can it be done with a single package? In
> On Sun, 09 Jul 2023, Mart Raudsepp wrote:
> Ühel kenal päeval, P, 09.07.2023 kell 10:10, kirjutas Sam James:
>>
>> zurabid2...@gmail.com writes:
>>
>> > I am new here, so I'm sorry in advance for any stupid thing I may
>> > say. I want to adopt hunspell for various reasons and what I've
LGTM except for a typo in the commit message:
> Adding a colon to the grep expression yeilds the desired result:
signature.asc
Description: PGP signature
> On Mon, 03 Jul 2023, Florian Schmaus wrote:
> So pkgcheck counting EGO_SUM entries would be sufficient for the
> purpose of having a static check that notices if the ebuild would
> likely run into the environment limit?
> To find a common compromise, I would possibly invest my time in
>
> On Wed, 28 Jun 2023, Florian Schmaus wrote:
> +# @FUNCTION: gradle-src_uri
> +# @DESCRIPTION:
> +# Generate SRC_URI data from EGRADLE_BUNDLED_VER.
> +gradle-src_uri() {
This is named gradle_src_uri (with two underscores) in the main eclass
documentation.
> +# @FUNCTION: gradle-src_unpack
> On Mon, 26 Jun 2023, Jaco Kroon wrote:
>> if [[ ${BUILD_DIR} != "${WORKDIR}"/* ]]; then
> BUILD_DIR="${WORKDIR}/../build"
Oh right, I hadn't thought about the case that the ebuild would override
it. (AFAICS cmake.eclass itself doesn't do .. in BUILD_DIR.)
> I know it's pathological ...
> On Mon, 26 Jun 2023, Sam James wrote:
> +
> + # Avoid creating ${WORKDIR}_build (which is above WORKDIR).
> + # TODO: For EAPI > 8, we should ban S=WORKDIR for CMake.
> + # See bug #889420.
> + if [[ ${S} == ${WORKDIR} && ${BUILD_DIR} ==
> On Tue, 13 Jun 2023, Michał Górny wrote:
> _pypi_normalize_name() {
> local name=${1}
> - local shopt_save=$(shopt -p extglob)
> - shopt -s extglob
> + local prev_extglob=-s
> + if ! shopt -p extglob >/dev/null; then
> + prev_extglob=-u
> +
> On Mon, 29 May 2023, Volkmar W Pogatzki wrote:
> +if [[ ${SLOT} = 0 ]]; then
> +: "${JAVA_LAUNCHER_FILENAME:=${PN}}"
> +else
> : "${JAVA_LAUNCHER_FILENAME:=${PN}-${SLOT}}"
> +fi
Please indent the lines in the then and else blocks.
signature.asc
Description: PGP signature
1 - 100 of 2165 matches
Mail list logo