Re: guidelines for package names (namespaces?)

John Kehayias writes: > Hi Andy, > > On Mon, Jul 03, 2023 at 01:55 PM, Andy Tai wrote: > >> Hi, in Guix there seems no guidelines for package names/namespaces >> although there are conventions like Python packages prefixed with >> python-... (good). However, this does not cover cases like Gn

Re: Guix's python has pip's user dir in its loadpath

Hi, On Sat, Jul 01, 2023 at 11:57 AM, Maxim Cournoyer wrote: > Hi, > > Wojtek Kosior writes: > >> The precedence of local, pip-installed Python libraries over Guix ones >> has already been a source of bugs. And these can be hard to diagnose. > >> I imagine an optimal solution would be to configu

Re: Transformations Shell Syntax

Hello, On Sun, Jul 02, 2023 at 09:54 PM, Ludovic Courtès wrote: > HI, > > John Kehayias skribis: > >> As one who also would like a shorter syntax option, here's a quick >> thought: what about a short version of what we have for when there >> is only one package given or it can be applied to all

Re: guidelines for package names (namespaces?)

Hi Andy, On Mon, Jul 03, 2023 at 01:55 PM, Andy Tai wrote: > Hi, in Guix there seems no guidelines for package names/namespaces > although there are conventions like Python packages prefixed with > python-... (good). However, this does not cover cases like Gnome > applications. For example, I

Re: Branch (and team?) for mesa updates

Hello, On Wed, Jul 05, 2023 at 08:08 PM, Andreas Enge wrote: > Am Wed, Jul 05, 2023 at 09:47:06AM -0600 schrieb Katherine Cox-Buday: >> I disagree with this because it seems like Mesa moves along at a pretty >> brisk pace and I feel like we'd be constantly recreating the same branch: >> 23.1.3, 2

Re: Branch (and team?) for mesa updates

Am Wed, Jul 05, 2023 at 09:47:06AM -0600 schrieb Katherine Cox-Buday: > I disagree with this because it seems like Mesa moves along at a pretty > brisk pace and I feel like we'd be constantly recreating the same branch: > 23.1.3, 2023-06-22 (14 days) > 23.1.2, 2023-06-08 ( 9 days) > 23.0.4, 2023-05

Re: Branch (and team?) for mesa updates

On 7/2/23 4:30 AM, Andreas Enge wrote: So I would suggest to delete every branch right after merging, and then branch off of master later when a new patch is going to be applied. This will also create a cleaner history by avoiding a merge. I disagree with this because it seems like Mesa moves