Re: Simple design question for schemers

Hi both of you, Am 25.02.24 um 11:05 schrieb Ricardo Wurmus: We have a macro called MODIFY-INPUTS, which you could use, but CONS* is probably enough in your case. Thanks. I'm using cons* now. cons* basically is the same the "extend" I'm used to from Python - sadly the Guile manual is so

Re: Simple design question for schemers

Hartmut Goebel writes: > Using a custom function "extend": > > (native-inputs > (extend %standard-trytond-native-inputs > trytond-account-invoice > trytond-purchase > trytond-sale)) We have a macro called MODIFY-INPUTS, which you could use, but

Re: Simple design question for schemers

Hi Hartmut, On Sat, 24 Feb 2024 21:47:41 +0800, Hartmut Goebel wrote: > > Hi, > > I'm about to refactor the Tryton packages to the (not so) new style. Now the > trytond-xxx modules all share a basic list of native > inputs,like this: > > (native-inputs >

Simple design question for schemers

Hi, I'm about to refactor the Tryton packages to the (not so) new style. Now the trytond-xxx modules all share a basic list of native inputs,like this:     (native-inputs `(,@(%standard-trytond-native-inputs)    ("trytond-account-fr"

Re: Question on python-pydantic update, rust and maturin build tool

Sharlatan Hellseher writes: > It might be addressed to rust/python teams. > https://github.com/pydantic/pydantic-core > > During update of some packages from (gnu packages astronomy) I've faced with > requirement for the fresh version of pydantic which > depends on pydantic-core built with

Re: Question on python-pydantic update, rust and maturin build tool

Hi Efraim, I was about to update python-hvpy to v1.1.0 which requires pydantic>=2.0.0 https://github.com/Helioviewer-Project/python-api/blob/v1.1.0/setup.cfg#L37 Pydantic 2+ (the latest is v2.5.3 2023-12-22) depends on pydantic-core (the latest is v2.14.6 2023-12-21) which is built with

Re: Question on python-pydantic update, rust and maturin build tool

On Tue, Dec 26, 2023 at 12:27:38AM +, Sharlatan Hellseher wrote: > Hi Guix! > > > It might be addressed to rust/python teams. > https://github.com/pydantic/pydantic-core > > During update of some packages from (gnu packages astronomy) I've faced > with requirement for the fresh version of

Question on python-pydantic update, rust and maturin build tool

Hi Guix! It might be addressed to rust/python teams. https://github.com/pydantic/pydantic-core During update of some packages from (gnu packages astronomy) I've faced with requirement for the fresh version of pydantic which depends on pydantic-core built with rust and maturin. This thread is

Re: Fw: Question regarding qmk firmware

John Kehayias writes: > Hello, > > On Sun, Oct 08, 2023 at 10:34 AM, Ekaitz Zarraga wrote: > >> Hi >> >> I want to forward this message to guix-devel because it is a clear >> case of some (actually good) technical decision affecting users in >> unexpected ways. >> >> Now, after the change, a

Re: Fw: Question regarding qmk firmware

Hi Ekaitz, Ekaitz Zarraga writes: > Hi > > I want to forward this message to guix-devel because it is a clear > case of some (actually good) technical decision affecting users in > unexpected ways. > > Now, after the change, a user might run `guix search avr-toolchain` and find > nothing.

Re: Fw: Question regarding qmk firmware

se it, and then one looks in the Guix manual how to add udev rules. Anyway, perhaps I run on a tangent here. John > I leave it as food for thought. > > Thanks, > > Ekaitz > > > --- Forwarded Message --- > From: Fredrik Salomonsson > Date: On Saturday, Octobe

Fw: Question regarding qmk firmware

, October 7th, 2023 at 21:23 Subject: Question regarding qmk firmware To: help-guix > Hi, > > Today I was tweaking a keymap for one of my qmk based keyboards but some > of the packages I used when building the firmware has been removed. My > commad was as follows: > > `sh gui

Re: to PR or not to PR, is /that/ the question?

Hi, On Thu, 14 Sept 2023 at 08:53, Giovanni Biscuolo wrote: > To remain /in topic/: I think that adopting a «web based PR model» will > definitely _not_ decrease the cognitive overhead for contributors. What could potentially decrease the cognitive overhead for contributors when using a "web

Re: to PR or not to PR, is /that/ the question?

Hi Simon Simon Tournier writes: > Thank you for your detailed message. Sorry, I have not read all the > details because I have been lost. Sorry! Forgive me since I am not able to summarize the details without losing content. > What do you want to explain? In the context of this increasing

Re: to PR or not to PR, is /that/ the question?

Hi Giovanni, Thank you for your detailed message. Sorry, I have not read all the details because I have been lost. What do you want to explain? Well, let me explain my understanding using my own words. :-) When one reduces to the core of the workflows, the main difference between “email

to PR or not to PR, is /that/ the question?

Hi Simon, please forgive me if I continue drifting in this beautiful sea... This message is /very/ long but it's just because I'm trying to do my best to provide a deep analisys of the **big** problems with eventually adopting a «web based PR model» (please see below for a definition) for

Re: Python Team: Keeping Branch Up To Date Question

So, I should add a Python teams specific section to the texinfo docs?

Re: Python Team: Keeping Branch Up To Date Question

Hi jgart, "jgart" writes: > Thanks, I ended up doing what you suggested. > > Should we document this git branch policy for contributors with commit access > in the manual? > > I think we should state it explicitly so there is no confusion for new > contributors with commit access. If

Re: Python Team: Keeping Branch Up To Date Question

Thanks, I ended up doing what you suggested. Should we document this git branch policy for contributors with commit access in the manual? I think we should state it explicitly so there is no confusion for new contributors with commit access. all best, jgart

Re: Python Team: Keeping Branch Up To Date Question

Hi, Lars-Dominik Braun writes: > Hi, > >> What is the git approach for keeping the Python branch up to date? 閭 >> Should I be rebasing off of master or something else? > > yeah, that’s generally what I would do before working on it. Note that > you cannot force-push into Savannah. You have to

Re: Python Team: Keeping Branch Up To Date Question

Hi, > What is the git approach for keeping the Python branch up to date? 閭 > Should I be rebasing off of master or something else? yeah, that’s generally what I would do before working on it. Note that you cannot force-push into Savannah. You have to remove the remote branch and create it again.

Re: package definition question: referring to source files of another package?

dy Tai: > > In some scenarios package A may refer to source files in package B. > > The question is, > > 1. How to reference source directory of package B from within > > definition of package A? > You can use (package-source B) both within source and inputs. The only

Python Team: Keeping Branch Up To Date Question

Hi Lars, What is the git approach for keeping the Python branch up to date? 閭 Should I be rebasing off of master or something else? I'm trying to review this patch: https://issues.guix.gnu.org/64973 Any advice much appreciated. all best, jgart

Re: package definition question: referring to source files of another package?

> In some scenarios package A may refer to source files in package B. depending on where and what you need, you can do something like this in a GEXP context: (define (upstream-file relative-path) (let ((git-origin (let ((commit "v0.13.2")) (origin (method

Re: package definition question: referring to source files of another package?

Am Samstag, dem 02.09.2023 um 20:35 -0700 schrieb Andy Tai: > Hi, this is a question for writing package definition. > > In some scenarios package A may refer to source files in package B. > The question is,  > 1. How to reference source directory of package B from within > def

package definition question: referring to source files of another package?

Hi, this is a question for writing package definition. In some scenarios package A may refer to source files in package B. The question is, 1. How to reference source directory of package B from within definition of package A? 2. can we even assume sources of Package B is available? Normally

Re: Can ALPS be included in the Guix repo? The question is about the licenses.

Hi, On Sun, 13 Aug 2023 at 17:31, Efraim Flashner wrote: > Placing the limitation of 'academic and non-commercial' the license is > non-free and cannot be included in Guix proper. If something depends on > it that you're looking to upstream it'll need to be buildable without > that library. >

Re: Can ALPS be included in the Guix repo? The question is about the licenses.

On Sat, Aug 12, 2023 at 04:03:31PM +0500, nigko wrote: > Hello Guix! > > The ALPS project* (Algorithms and Libraries for Physics Simulations) > https://web.archive.org/web/20210508050408/https://alps.comp-phys.org/mediawiki/index.php/Main_Page > is an open source effort aiming at providing

Can ALPS be included in the Guix repo? The question is about the licenses.

Hello Guix! The ALPS project* (Algorithms and Libraries for Physics Simulations) https://web.archive.org/web/20210508050408/https://alps.comp-phys.org/mediawiki/index.php/Main_Page is an open source effort aiming at providing simulation codes for strongly correlated quantum mechanical systems

package definition question: installation into system directory

Hi, I was trying to create a package definition for xrdp. when testing the package build, its fails at installation step: libtool: install: /gnu/store/a5i8avx826brw5grn3n4qv40g514505c-coreutils-9.1/bin/install -c .libs/xrdp-sesman

Re: package definition question: installation into system directory

Hi Andy, On Fri, Jun 23, 2023 at 11:44 AM Andy Tai wrote: > > Hi, I was trying to create a package definition for xrdp. > > cannot create directory ‘/etc/xrdp’: Permission denied Installation paths must be located inside the output folder. The paths always point into the store. > make[3]: ***

package definition question: installation into system directory

Hi, I was trying to create a package definition for xrdp. when testing the package build, its fails at installation step: libtool: install: /gnu/store/a5i8avx826brw5grn3n4qv40g514505c-coreutils-9.1/bin/install -c .libs/xrdp-sesman

Re: Question about packaging TexLive

Nicolas Goaziou writes: >>> 2. Some affected packages are also missing propagated inputs (e.g., >>>texlive-latex-graphics for texlive-latex-fncychap); >> >> Correct. The old importer didn’t know about dependencies. The newer >> importer uses tlpdb to get a list of dependencies. > >

Re: Question about packaging TexLive

Am Wed, Apr 19, 2023 at 01:47:16PM +0200 schrieb Nicolas Goaziou: > AFAIU, this is not sufficient. All dependencies do not appear in > "texlive.tlpbd". For example, `texlive-halloweenmath' has no "depend" > entry in the tlpbd. Yet, it requires both texlive-amsmath and > texlive-pict2e (i.e.,

Re: Question about packaging TexLive

the same length. However, some packages do use "#:trivial #t" even though they should not, e.g., `texlive-latex-marginfix'. My point is that we should not make "#:trivial #t" the default, assuming that was a possibility stemming from Simon's question. >> 2. Some affect

Re: Question about packaging TexLive

Nicolas Goaziou writes: > Hello, > > Simon Tournier writes: > >> Other said, any objection to go from this pattern: >> >> --8<---cut here---start->8--- >> (define-public texlive-foo >> (package >> (name "texlive-foo") >> (version (number->string

Re: Question about packaging TexLive

Hello, Simon Tournier writes: > Other said, any objection to go from this pattern: > > --8<---cut here---start->8--- > (define-public texlive-foo > (package > (name "texlive-foo") > (version (number->string %texlive-revision)) > (source (origin

Question about packaging TexLive

Hi, CC: TeX team For context, TeX (broad meaning) is deep in the graph, thus its preservation is important when considering time-travel. And because TeX packages relies on Subversion, it raises some questions – for the interesting reader, see [1]. Here, I would like to open a discussion about

Re: Question on the process of packge withdrawal

On +2023-02-28 18:16:18 +0100, Simon Tournier wrote: > Hi, > > On Tue, 28 Feb 2023 at 17:26, wrote: > > > IMO, it's a matter of storing the junk where it will not be a toxic > > liability > > and nuisance, yet easily discovered by someone looking for "parts." > > Well, I will not call that

Re: Question on the process of packge withdrawal

Hi, On Tue, 28 Feb 2023 at 17:26, wrote: > IMO, it's a matter of storing the junk where it will not be a toxic liability > and nuisance, yet easily discovered by someone looking for "parts." Well, I will not call that "junk". :-) IMHO, this is discoverable since it is part of the Git history

Re: Question on the process of packge withdrawal

On Tue, Feb 28, 2023 at 03:57:33PM +0100, Andreas Enge wrote: > Updating packages that noone is interested in is an unnecessary drag > on volunteers' time. This is the key point, in my opinion. Those who wanted to use this package were very welcome to do something about it. And they are still

Re: Question on the process of packge withdrawal

Hi, On +2023-02-28 11:30:21 +0100, Simon Tournier wrote: > > I proposed to remove the package because it was broken and no one was > willing to fix it. What is the point to keep broken packages? > What is the purpose of a junk-yard for broken cars? I think there is some use :) I kept an old

Re: Question on the process of packge withdrawal

Hello, Am Sun, Feb 26, 2023 at 08:11:52PM + schrieb Sharlatan Hellseher: > If we check > > > commit removing jrnl variable which has it's source pointing to >

Re: Question on the process of packge withdrawal

Hi, On dim., 26 févr. 2023 at 20:11, Sharlatan Hellseher wrote: > Other example > > > the reason it's not updated at - > development was moved to

Re: Question on the process of packge withdrawal

On Mon, Feb 27, 2023, at 12:12, Maxim Cournoyer wrote: > I think packages removal should go to the patch tracker, with a CC to > guix-devel to give more visibility to let time for all parties to > comment or find a solution (perhaps a maintained fork exists, etc.) I agree that removal should go

Re: Question on the process of packge withdrawal

Hi, Sharlatan Hellseher writes: [...] > Other example > > > the reason it's not updated at - > development was moved to .

Question on the process of packge withdrawal

Hi Guix! I've noticed a tendency in core-updates and staging of withdrawing old packages, packages which were created from forks in the past or packages failing to build due to increased complexity of the package. If we check

Re: Fwd: question on setting up guix.scm for project development

nks. > >guix shell -D -f guix.scm > >did work for me I did not see d2 0.1.4 from > > >guix package --list-installed >or >guix package --list-available >but > >pkg-config --modversion d2 > >did show 0.1.4 So it is there, in this guix shell. > >Thanks f

Re: Fwd: question on setting up guix.scm for project development

Hi, thanks. guix shell -D -f guix.scm did work for me I did not see d2 0.1.4 from guix package --list-installed or guix package --list-available but pkg-config --modversion d2 did show 0.1.4 So it is there, in this guix shell. Thanks for all the replies to this question. On Mon, Nov

Re: Fwd: question on setting up guix.scm for project development

up an environment containing all the >dependencies for development of a package; this can be done via a >guix.scm file containing the package definition. > >My question is, if I am developing a package which has dependencies >with newer versions than what is available in the guix re

Re: Fwd: question on setting up guix.scm for project development

.scm file containing the package definition. > > My question is, if I am developing a package which has dependencies > with newer versions than what is available in the guix repo, how can I > use the guix.scm file to bring in the new version of the dependencies? > As an example:

Fwd: question on setting up guix.scm for project development

Hi, guix allows setting up an environment containing all the dependencies for development of a package; this can be done via a guix.scm file containing the package definition. My question is, if I am developing a package which has dependencies with newer versions than what is available

Re: Question: wrap-program without #:sh can be ok even when cross-compiling?

Am Sonntag, den 06.06.2021, 12:14 +0200 schrieb Maxime Devos: > Leo Prikler schreef op zo 06-06-2021 om 09:39 [+0200]: > > I think we might want to export a utility procedure > > (patch-shebangs files inputs) > > This procedure already exists, but is undocumented and > unexported. It is in

Re: Question: wrap-program without #:sh can be ok even when cross-compiling?

Leo Prikler schreef op zo 06-06-2021 om 09:39 [+0200]: > I think we might want to export a utility procedure > (patch-shebangs files inputs) This procedure already exists, but is undocumented and unexported. It is in (guix build gnu-build-system). (define* (patch-shebangs #:key inputs

Question: wrap-program without #:sh can be ok even when cross-compiling?

I think we might want to export a utility procedure (patch-shebangs files inputs) so that files used during build (e.g. configure, Makefile, etc.) can do (patch-shebangs build-stuff native-inputs) and the rest implicitly gets (patch-shebangs files inputs) during the patch-shebangs phase.

Question: wrap-program without #:sh can be ok even when cross-compiling?

About (the ‘wrap-program #:sh’ patch series): While looking at guix/build/gnu-build-system.scm, I noticed the 'patch-shebangs' phase, which is run after the install phase. IIUC, this phase is for changing shebangs ... #!/usr/bin/stuff to ...

Re: newbe question

o, thank you. i haven't checked. this is a new file? anyway, thank you for your message May 11, 2021, 14:53 by bone.bab...@disroot.org: > Adam Kandur via Development of GNU Guix and the GNU System distribution. > writes: > >> hi everyoone! is there any example of packed racket code? >> >

Re: newbe question

Adam Kandur via Development of GNU Guix and the GNU System distribution. writes: > hi everyoone! is there any example of packed racket code? The Guix repository has a file for racket packages `/gnu/packages/racket.scm`. You can look at this file here

newbe question

hi everyoone! is there any example of packed racket code?

Re: Question about compile packages

Hello Mark, On Wed, Mar 31, 2021 at 2:30 AM Mark H Weaver wrote: > If more people are interested in using Guix in this way, the experience > could probably be made much nicer. I think this would interest quite a few people, a guixtoo cookbook chapter ? I've wondered about such subject myself

Re: Question about compile packages

On Tue, 30 Mar 2021 07:12:27 -0400 Julien Lepiller wrote: > Not sure about your first question. Maybe create your own fork and > regularly rebase it? Guix will not be very happy with that I think, > but it should work. > > To pass --no-substitutes, you can pass it to guix-da

Re: Question about compile packages

ve so global as I already mentioned, so that these > are added to each package at the time of compilation, this would not be > within the guix development environment, because what I want is that this > compilation is natively for my pc. Julien Lepiller replied: > Not sure about you

Re: Question about compile packages

Not sure about your first question. Maybe create your own fork and regularly rebase it? Guix will not be very happy with that I think, but it should work. To pass --no-substitutes, you can pass it to guix-daemon, or remove the authorized keys from /etc/guix/acl. The second option lets you

Question about compile packages

that these are added to each package at the time of compilation, this would not be within the guix development environment, because what I want is that this compilation is natively for my pc. As a second question, how could I set the --no-susbtitutes option when installing the guix system from ISO

Re: Question about Guix on Novena - mainly U-Boot

On Fri, 4 Dec 2020 19:49:37 +0100 Danny Milosavljevic wrote:> > Now I want to make it boot it from SATA instead. The question is what "boot from SATA" means here, it could mean different things: - Have u-boot on the microSD card and load the rootfs from the SATA HDD/SSD. -

Question about Guix on Novena - mainly U-Boot

Hi Danny! You may want to try to set "CONFIG_PREBOOT=\"usb start; sata init; part list sata 0 -bootable devplist\"". I do something similar to execute "dhcp" to enable booting via tftp. Maybe take a look at my recent patch¹ as well, which aims to ease such configuration changes. Bye Stefan

Re: Question about Guix on Novena - mainly U-Boot

For reference, the config.scm I used was: (use-modules (gnu) (gnu bootloader u-boot)) (use-service-modules networking ssh desktop) (use-package-modules bootloaders screen ssh linux) ;;; Note: Maybe better: linux-libre-arm-generic ;;; Note: Novena upstream uses Kernel 3.19 (operating-system

Question about Guix on Novena - mainly U-Boot

Hi, I'm still in the process of setting up the Novena as a GNU Mes for ARM build machine. Guix system on Novena from sd card finally works. Now I want to make it boot it from SATA instead. So I did the following: (1) Used cp -a to copy over everything from the sd card / to the sata drive

Re: File search progress: database review and question on triggers

Ludovic Courtès writes: > A client-side approach (not involving guix-daemon) would be more readily > usable, though some of the questions above remain open. I'd also prefer to stick to the client side. But how can I trigger an event when a package gets built? Maybe we could hook into specific

Re: File search progress: database review and question on triggers

Pierre Neidhardt skribis: > Ludovic Courtès writes: > >> It first tries ‘query-path-info’, which succeeds if the store item is >> available and contains info about its size, references, and so on. >> >> When ‘query-path-info’ fails, it falls back to >> ‘query-substitutable-path-info’, which

Re: File search progress: database review and question on triggers

Pierre Neidhardt writes: > So we could do the same with `guix filesearch`: > > - First try the entry in the database. > > - If not there, try query-path-info and if it succeeds, populate the > database. > > - If query-path-info does not succeed, try our new >

Re: File search progress: database review and question on triggers

Pierre Neidhardt skribis: > Ludovic Courtès writes: > >>> Question: How do I hook onto =guix build=? >> >> You would need a build-completion hook in the daemon, which doesn’t >> exist (yet!). Note also that at this level we only see derivations, not >>

Re: File search progress: database review and question on triggers

Ludovic Courtès writes: >> Question: How do I hook onto =guix build=? > > You would need a build-completion hook in the daemon, which doesn’t > exist (yet!). Note also that at this level we only see derivations, not > packages. Hmm... Can you explain me how =guix size= works

Re: File search progress: database review and question on triggers

k we need to think about integrating it maybe with >> ‘guix publish’ on the server side and (guix channels) on the client >> side. > > If the database is filled on =guix build=, then the substitute server > would automatically have a filesearch database. > > Question: How d

Re: File search progress: database review and question on triggers

l", so that > the "filesearch" subcommand would not download anything. Like substitutes, it should be an optional feature IMO, which means we need to keep clear boundaries. There’s also the question of whether we should have a system-wide database so that each user doesn’t have to

Re: File search progress: database review and question on triggers

Hi Pierre, Pierre Neidhardt skribis: > Ludovic Courtès writes: [...] >> It would be nice to see whether/how this could be integrated with >> third-party channels. Of course it’s not a priority, but while >> designing this feature, we should keep in mind that we might want >> third-party

Re: File search progress: database review and question on triggers

On Mon, 12 Oct 2020 at 12:20, Ludovic Courtès wrote: >> - Textual database: slow and not lighter than SQLite. Not worth it I >> believe. >> >> - SQLite without full-text search: fast, supports classic patterns >> (e.g. "foo*bar") but does not support word permutations. >> >> - SQLite with

Re: File search progress: database review and question on triggers

Hi, Pierre Neidhardt skribis: > Of course, `guix filesearch` hasn't been implemented yet ;) > > We still need to decide whether we want to make it part of `guix search' > or define a separate command. I would lean towards keeping it separate, so that it’s an optional feature (given that it

Re: File search progress: database review and question on triggers

Hi! Pierre Neidhardt skribis: >> Could you post a summary of what you have done, what’s left to do, and >> how you’d like to integrate it? (If you’ve already done it, my >> apologies, but you can resend a link. :-)) > > What I've done: mostly a database benchmark. > > - Textual database: slow

Re: File search progress: database review and question on triggers

On Sun, 11 Oct 2020 at 16:25, Pierre Neidhardt wrote: > Maybe you misunderstood a point: the filesearch database is not a > database of _all store items_, but only of the items that correspond to > the packages of a given Guix generation. Yes, it is clear for me. I meant: “all the store items

Re: File search progress: database review and question on triggers

Hi Pierre, I am trying to resume the work on "guix search" to improve it (faster). That's why I am asking the details. :-) Because with the introduction of this database, as mentioned earlier, 2 annoyances could be fixed at once. On Sun, 11 Oct 2020 at 13:19, Pierre Neidhardt wrote: > >

Re: File search progress: database review and question on triggers

Hi Zimoun, Thanks for the feedback! > --8<---cut here---start->8--- > echo 3 > /proc/sys/vm/drop_caches > time updatedb --output=/tmp/store.db --database-root=/gnu/store/ > > real0m19.903s > user0m1.549s > sys 0m4.500s I don't know the size of

Re: File search progress: database review and question on triggers

Hi, On Mon, 05 Oct 2020 at 20:53, Pierre Neidhardt wrote: > - Textual database: slow and not lighter than SQLite. Not worth it I believe. Maybe I am out-of-scope, but re-reading *all* the discussion about “fileserch”, is it possible to really do better than “locate”? As Ricardo mentioned.

Re: File search progress: database review and question on triggers

Hi, On Sat, 10 Oct 2020 at 10:57, Pierre Neidhardt wrote: > Of course, `guix filesearch` hasn't been implemented yet ;) Sorry, I have overlooked the status. :-) > We still need to decide whether we want to make it part of `guix search' > or define a separate command. >From my point of view,

Re: File search progress: database review and question on triggers

Of course, `guix filesearch` hasn't been implemented yet ;) We still need to decide whether we want to make it part of `guix search' or define a separate command. Thoughts? -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: File search progress: database review and question on triggers

Hi Pierre, On Mon, 5 Oct 2020 at 20:53, Pierre Neidhardt wrote: > Comments and help welcome! :) I have just checked out and I am probably failing but "./pre-inst-env guix filesearch whatever" raises an error with the backtrace: --8<---cut here---start->8---

Re: File search progress: database review and question on triggers

Hi Ludo! Ludovic Courtès writes: > Nice! Thanks! > Could you post a summary of what you have done, what’s left to do, and > how you’d like to integrate it? (If you’ve already done it, my > apologies, but you can resend a link. :-)) What I've done: mostly a database benchmark. - Textual

Re: File search progress: database review and question on triggers

Hi, Pierre Neidhardt skribis: > I've pushed a commit which adds the synopsis and the description to the > database. > > 0127cfa5d089857a716bf7b0a167f31cc6dd > > The quite surprising result is that these new details only cost 1 MiB extra! > > I can then search packages and it's super fast: >

Re:Re: Packaging question: Backport patch or use newer commit?

t;> latest release(v1.13.0) failed to build with Qt 5.14. And it was fixed in >> https://github.com/wang-bin/QtAV/commit/5abba7f0505e75fc. The question is: >> "Should I backport this fix to v1.13.0 or just use this commit to build >> qtav?" >> >> >>

Re: Packaging question: Backport patch or use newer commit?

ttps://github.com/wang-bin/QtAV/) first, but it's > latest release(v1.13.0) failed to build with Qt 5.14. And it was fixed in > https://github.com/wang-bin/QtAV/commit/5abba7f0505e75fc. The question is: > "Should I backport this fix to v1.13.0 or just use this commit to build qtav?&

Packaging question: Backport patch or use newer commit?

uild with Qt 5.14. And it was fixed in https://github.com/wang-bin/QtAV/commit/5abba7f0505e75fc. The question is: "Should I backport this fix to v1.13.0 or just use this commit to build qtav?" If there're some guidelines on this, please tell me, thanks a lot! -- Zihao

Re: File search progress: database review and question on triggers

> There is a subtle different: in the latter, (search-file-package) is > allowed and won't trigger a compile time error, while the former does. > This "foo . more-foo" paradigm is a way to say "1 or more arguments", > instead of "0 or more". Ah, ok, that makes sense! Regards, Arun

Re: File search progress: database review and question on triggers

> Oops! Forgot to push. > > It's actually commit 25147f983bdf432b03e8271abe0318f4812f94ba on > wip-filesearch. I checked and it works now. Just a tiny nitpick: The function signature of search-file-package, --8<---cut here---start->8--- (define

Re: File search progress: database review and question on triggers

Hi Pierre! Sorry for the very late response. > I've fixed it in > e08f913d20428a9a925cc46d177c7446f55e6443. The downside is that we can't > use any special character like boolean operators. I'm not sure how we > can get the best of both worlds. Maybe add a command line flag that > would

Re: File search progress: database review and question on triggers

zimoun writes: > I am not sure to see how. One needs all the database to search inside > and cannot know in advance which packages etc.. Contrary to “guix size” > which manipulates the graph and then download the missing parts. > > Therefore, your suggestion is to download all the database the

Re: File search progress: database review and question on triggers

Hi Pierre, On Thu, 27 Aug 2020 at 13:15, Pierre Neidhardt wrote: > zimoun writes: > >> If you are going to an local SQL database, my two questions are: >> >> a) >> Which part would update it? “guix pull”? Other? Even using >> substitutes, the channels and co could lead to an extra cost and

Re: File search progress: database review and question on triggers

Hi Simon! zimoun writes: > If you are going to an local SQL database, my two questions are: > > a) > Which part would update it? “guix pull”? Other? Even using > substitutes, the channels and co could lead to an extra cost and so what > is acceptable and what is not? I suggest fetching

Re: File search progress: database review and question on triggers

Hi Pierre, Cool to relive the topic. :-) (disclaim: I have not yet process all the thread and emails) On Mon, 10 Aug 2020 at 16:32, Pierre Neidhardt wrote: > 1. An SQLite database with the following schema: If you are going to an local SQL database, my two questions are: a) Which part

Re: File search progress: database review and question on triggers

>> - You should use SQL prepared statements with sqlite-prepare, >> sqlite-bind, etc. That would correctly handle escaping special >> characters in the search string. Currently, searching for >> "transmission-gtk", "libm.so", etc. errors out. > > Thanks for pointing this out, I'll look into

Re: File search progress: database review and question on triggers OFF TOPIC PRAISE

Thanks for working on this! This is a super awesome feature! Best of luck! -- Joshua Branson Sent from Emacs and Gnus

  1   2   3   4   >