On 2023-01-24 18:11, Michał Górny wrote:
> How many packages do you expect to add to this new category? It's not
> customary to create a new category for one package.
Look at www-servers/nginx package, it's huge! Lots of modules
(many of them are 3rd-party) could be separate packages.
On 2023-01-30 12:00, Michał Górny wrote:
> However, there's a can of worms around the corner -- should we also
> allow normalizing "-" and "_" across different packages (see dev-
> python/sphinx*)?
PyPI treats "-" and "_" separators as the same, so I'd not use
underscores for in-repo consistency.
No objections. Lots of work though :)
I'd prefer if PyPI names are guidelines, not a strict policy. I don't
like CamelCase and separators other than dash ("-") :P
Also I don't like when packages are named "dev-python/python-foo"
instead of just "dev-python/foo".
On 2023-01-28 19:02, Ulrich Mueller wrote:
> > On Sat, 28 Jan 2023, Michał Górny wrote:
> >> However, it's been pointed out that this makes it hard for people to
> >> find packages they're looking for.
>
> I don't understand this argument. Why would all-lowercase make finding a
> package
Much wanted eclass. Thanks!
On 2023-03-25 09:18, Hans de Graaff wrote:
> Signed-off-by: Hans de Graaff
> ---
> eclass/ruby-fakegem.eclass | 9 +
> eclass/ruby-ng.eclass | 25 +
> 2 files changed, 34 insertions(+)
>
> diff --git a/eclass/ruby-fakegem.eclass b/eclass/ruby-fakegem.eclass
Is it better than
RESTRICT="test"
?
On 2023-04-17 09:37, Florian Schmaus wrote:
> The EGO_SUM alternatives
> - do not have the same level of trust and therefore have a negative
> impact on security (a dubious tarball someone put somewhere, especially
> when proxy-maint)
Solution: generate release tarballs in upstream CI/CD.
> -
On 2023-04-25 16:09, Maciej Barć wrote:
> You would also have to have correct permissions on cache dirs
> (root:portage or portage:portage) this also means that the cache dir
> will have to be set during build explicitly.
> Do both Nim and Go support setting it?
Yes. For Nim it would be
Hello,
Portage can use ccache and sccache to speed up builds, but some
languages (like Go and Nim) support caches out-of-the-box. It's not fair
that we can't use them.
I'd like to start discussion on this topic. What should be the preferred
method of handling build caches?
I think adding more
> dev-lang/crystal
> dev-util/shards
These packages are only used in ::guru, so they could be moved there.
On 2023-07-11 08:41, TrakRailySurely wrote:
> Hello Everyone.
>
> When one package has another library that only depends on that package,
> should that library be statically linked?
> For example, the library aws-crt-cpp on which aws-sdk-cpp depends.
> This package only depends on aws-sdk-cpp.
On 2023-05-30 17:52, Florian Schmaus wrote:
> To prevent harm from Gentoo, we should reach an agreement that everyone
> can live with. To achieve a consensus, and since I can not rule out that
> I missed a post that includes specific numbers, please share your ideas
> on how EGO_SUM could be
Hi lists,
You might know about the `app-portage/metagen` utility that generates
metadata.xml files with your name and email. But there was no tool that
autofilled upstream information, so I wrote it.
Using it is as simple as:
$ gentle foo-0.1.ebuild
You can install it as
TL;DR:
Install:
# eselect repository enable guru && emaint sync -r guru
# emerge dev-util/find-work
Browse documentation:
$ xdg-open https://find-work.sysrq.in/
$ man find-work
Backstory
-
I used to be very active in ::guru, trying to
16 matches
Mail list logo
