>> - 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
Thanks for working on this! This is a super awesome feature! Best of luck!
--
Joshua Branson
Sent from Emacs and Gnus
Am 15.08.20 um 23:20 schrieb Bengt Richter:
> If you are on debian, have you tried
> dpkg -l '*your*globbed*name*here*'
No, since for Debian I'm not using a command-line tool, but the
Web-Interface - which allows querying even packages I have not
installed. (And the later is my specific
Hi Hartmut, et al
On +2020-08-15 14:47:12 +0200, Hartmut Goebel wrote:
> Am 13.08.20 um 12:04 schrieb Pierre Neidhardt:
> > SQLite pattern search queries are extremely fast (<0.1s) and cover all
> > examples named so far:
> >
> > - exact basename match
> > - partial path match
> > - pattern match
Hi Pierre,
I tried the wip-filesearch branch. Nice work! :-)
persist-all-local-packages takes around 350 seconds on my machine (slow
machine with spinning disk) and the database is 50 MB. Some other
comments follow.
- Maybe, we shouldn't index hidden files, particularly all the .xxx-real
Am 11.08.20 um 14:35 schrieb Pierre Neidhardt:
> Unlike Nix, we would like to do more than just index executable files.
> Indeed, it's very useful to know where to find, say, a C header, a .so
> library, a TeXlive .sty file, etc.
+1
Most of the time I'm searching for non-executable files.
--
Am 13.08.20 um 12:04 schrieb Pierre Neidhardt:
> SQLite pattern search queries are extremely fast (<0.1s) and cover all
> examples named so far:
>
> - exact basename match
> - partial path match
> - pattern match (e.g. "/include/%foo%")
For comparison: These are the options Debian Package search
I've pushed my experiment to the `wip-filesearch' branch.
As of this writing it is not automatically triggered by "guix build".
To test it:
- Load the module from a REPL.
- Run
--8<---cut here---start->8---
(test-index-git)
--8<---cut
Arun Isaac writes:
> But filenames usually don't have diacritics. So, I'm not sure if
> diacritic insensitivity is useful.
Probably not, but if there ever is this odd file name with an accent,
then we won't have to worry about it, it will be handled. Better too
much than too little!
> This is
> Yes, but full text search brings us a few niceties here:
These are nice features, but I don't know if all of them are useful for
file search. Normally, with Arch's pkgfile, I seach for some missing
header file, shared library, etc. Usually, I know the exact filename I
am looking for, or I know
Ricardo Wurmus writes:
> Pierre Neidhardt writes:
>
>> - Or do you think SQLite patterns (using "%") would do for now? As
>> Mathieu pointed out, it's an unfortunate inconsistency with the rest of
>> Guix. But maybe regexp support can be added in a second stage.
>
> These patterns could
>> sqlite insert statements can be very fast. sqlite.org claims 5
>> or...
>
> I tried it, and got it down to... 30s!
That's great! :-)
> - Or do you think SQLite patterns (using "%") would do for now? As
> Mathieu pointed out, it's an unfortunate inconsistency with the rest of
> Guix.
Pierre Neidhardt writes:
> - Or do you think SQLite patterns (using "%") would do for now? As
> Mathieu pointed out, it's an unfortunate inconsistency with the rest of
> Guix. But maybe regexp support can be added in a second stage.
These patterns could be generated from user input that
Pierre Neidhardt writes:
> Julien Lepiller writes:
>
>> Why wouldn't it help? Can't you make it a trie from basename ->
>> complete name? If I'm looking for "libcord.so" (which is a key in the
>> trie), I don't think I need to look for every path. I only need to
>> follow the trie until I
Hi Ricardo,
Ricardo Wurmus writes:
>> Why wouldn't it help? Can't you make it a trie from basename -> complete
>> name? If I'm looking for "libcord.so" (which is a key in the trie), I don't
>> think I need to look for every path. I only need to follow the trie until I
>> find a pointer to
Hi,
> 1. I tried to fine-tune the SQL a bit:
> - Open/close the database only once for the whole indexing.
> - Use "insert" instead of "insert or replace".
> - Use numeric ID as key instead of path.
>
> Result: Still around 15-20 minutes to build. Switching to numeric
> indices shrank
Julien Lepiller writes:
> Why wouldn't it help? Can't you make it a trie from basename -> complete
> name? If I'm looking for "libcord.so" (which is a key in the trie), I don't
> think I need to look for every path. I only need to follow the trie until I
> find a pointer to some structure
Why wouldn't it help? Can't you make it a trie from basename -> complete name?
If I'm looking for "libcord.so" (which is a key in the trie), I don't think I
need to look for every path. I only need to follow the trie until I find a
pointer to some structure that contains the data I look for
Pierre Neidhardt writes:
> Result: Takes between 20 and 2 minutes to complete and the result is
> 32 MiB big. (I don't know why the timing varies.)
Typo: 20 _seconds_ to 2 minutes! So it's faster than SQL by 1 or 2 orders of
magnitude.
--
Pierre Neidhardt
https://ambrevar.xyz/
2 MiB big. (I don't know why the timing varies.)
>
> A string-contains filter takes less than 1 second.
>
> A string-match (regex) search takes some 3 seconds (Ryzen 5 @ 3.5
> GHz). I'm not sure if we can go faster. I need to measure the time
> SQL takes for a
Pierre Neidhardt writes:
> Pierre Neidhardt writes:
>
>> Ricardo Wurmus writes:
>>
>>> I’m not suggesting to use updatedb, but I think it can be instructive to
>>> look at how the file database is implemented there. We don’t have to
>>> use SQlite if it is much slower and heavier than a
Ricardo Wurmus writes:
> Oof. The updatedb hack above takes 6 seconds on my i7-6500U CPU @
> 2.50GHz with SSD.
>
> I’m not suggesting to use updatedb, but I think it can be instructive to
> look at how the file database is implemented there. We don’t have to
> use SQlite if it is much slower
Pierre Neidhardt writes:
> 3. Size of the database:
>I've persisted all locally-present store items for my current Guix version
>and it produced a database of 72 MiB. It compresses down to 8 MiB
>in zstd.
For comparison, my laptop’s store contains 1,103,543 files, excluding
ould only store the
"diffs" between the Guix generations. I don't know if SQLite supports
this. If not, it sounds like a rather complex thing to do.
But really, if the compressed database over multiple Guix generations is
<100 MiB, then size is not a big problem.
>>
ge X produces [Y1, Y2, ...] executable files. Then
on package X update, the executable files list could be refreshed.
>Question: Should we include empty directories in the database? I'm tempted
>to answer no.
I would also say no, and also exclude non-executable files.
>Question
dexing will be done by the substitute servers however, so this
is
of little concern for the end user.
Question: Should we include empty directories in the database? I'm tempted
to answer no.
5. Search speed: It completes in a fraction of a second and supports
SQLite patterns. Example:
On Sat, Feb 29, 2020 at 7:34 PM Leo Famulari wrote:
> These URLs provide content-addressed mirrors that Guix always falls back to
> when it cannot download the file in the "normal" way, which in that case
> would be the GNOME mirrors. They are defined in 'guix/download.scm'.
Thanks for the
On Sat, Feb 29, 2020 at 11:37:19AM +0100, Vincent Legoll wrote:
> https://ci.guix.gnu.org
> https://tarballs.nixos.org
> https://archive.softwareheritage.org
[...]
> but when reading guix/download.scm, I don't find those urls listed for
> the gnome mirror, what I am missing ?
These URLs
answering to myself (I should have searched before asking)...
The 3.22.10 version has been tagged in gitlab, but the tarball
still isn't available on the official gnome download site, that
should probably explain what's happening.
Sorry for the noise.
--
Vincent Legoll
Hello,
I was trying to update aisleriot, which uses the mirror://gnome/ to
download source, it failed with a 404 on the following servers:
https://ci.guix.gnu.org
https://tarballs.nixos.org
https://archive.softwareheritage.org
It is not on nixos mirror, probably because they're still on an
Pierre Neidhardt skribis:
> I've merged your last 3 patches, thank you so much for your continuous
> contribution to the best Common Lisp package manager ;)
Thanks!
Pierre Neidhardt skribis:
> Great! :)
> Can you send a patch for all this? I'll merge as soon as I can.
I sent the patches (bug#37791).
Pierre Neidhardt skribis:
> Cool! Thanks for working on this! :)
>
> Does it work for dexador?
I just tried compiling ecl-dexador, and it failed. However I think it
fails for a different reason.
The error is:
--8<---cut here---start->8---
An error
Pierre Neidhardt skribis:
> Maybe an easier fix: replace "sbcl" with (%lisp-type). Should work.
Indeed, with the following changes, building ecl-dexador works.
--8<---cut here---start->8---
diff --git a/gnu/packages/lisp.scm b/gnu/packages/lisp.scm
index
Pierre Neidhardt skribis:
> Cool! Thanks for working on this! :)
>
> Does it work for dexador?
I just tried compiling ecl-dexador, and it failed. However I think it
fails for a different reason.
The error is:
--8<---cut here---start->8---
An error
Guillaume Le Vaillant writes:
> I just tried compiling ecl-dexador, and it failed. However I think it
> fails for a different reason.
>
> The error is:
>
> --8<---cut here---start->8---
> An error occurred during initialization:
> No MIME.TYPES file found
Guillaume Le Vaillant skribis:
> However, when I try to compile 'ecl-simple-parallel-tasks', guix first
> tries to build a different derivation of 'ecl-chanl', which fails
> because it apparently doesn't have the modified phases declared in the
> definition of 'ecl-chanl'.
I was able to get
Efraim Flashner skribis:
> On Wed, Oct 16, 2019 at 01:59:01PM +0200, Pierre Neidhardt wrote:
>> I've encountered the same problem a couple of times.
>> If you try to compile ecl-dexador, you'll see it fails because it does
>> not re-use the arguments of sbcl-dexador which patches out a failing
On Wed, Oct 16, 2019 at 01:59:01PM +0200, Pierre Neidhardt wrote:
> I've encountered the same problem a couple of times.
> If you try to compile ecl-dexador, you'll see it fails because it does
> not re-use the arguments of sbcl-dexador which patches out a failing
> test.
>
> Something is wrong
I've encountered the same problem a couple of times.
If you try to compile ecl-dexador, you'll see it fails because it does
not re-use the arguments of sbcl-dexador which patches out a failing
test.
Something is wrong in sbcl-package->ecl-package.
Andy?
That said, it's not a very big deal, since
Hi,
I'm trying to package a Common Lisp library and I have a strange
problem.
In 'gnu/packages/lisp.scm', there are packages called 'sbcl-chanl' and
'ecl-chanl' whose definitions are:
--8<---cut here---start->8---
(define-public sbcl-chanl
(let ((commit
* Hartmut Goebel [2019-10-10 10:26]:
> Am 10.10.19 um 06:30 schrieb Jean Louis:
> > They want take over, obviously, so they said.
> […]
> > They are indirectly asking for money. GNU project is about money,
>
> Both of these are allegation missing any backing.
Oh, is that a principle that
Am 09.10.19 um 22:39 schrieb František Kučera:
> Dne 09. 10. 19 v 19:06 P napsal(a):
>> Stop spamming the list. Thanks.
>>
> If you did not want to start this discussion, you should not have
> posted that statement on the official Guix blog. You could expect what
> it would do.
"P" is not one of
Am 10.10.19 um 06:30 schrieb Jean Louis:
> They want take over, obviously, so they said.
[…]
> They are indirectly asking for money. GNU project is about money,
Both of these are allegation missing any backing.
I strongly suggest you stop attacking the persons on a personal level,
but instead
* Svante Signell [2019-10-09 19:19]:
> Dear Guix, and other people signing that statement.
> cc: RMS
>
> I do also have problems with your campaign against RMS. Publishing such
> a statement as a blog entry for Guix is very inappropriate. Especially
> in the context of the recent defaming
* František Kučera [2019-10-09 18:11]:
> Dne 09. 10. 19 v 23:41 Wilson Bustos napsal(a):
> > Seems they don't want to reply, probably because they don't have argument.
> > Also, the project signs without as anyone to do it, they just did it.
> > There is not a vote to say 'The project is agree
* Wilson Bustos [2019-10-09 17:41]:
> Jean Luis,
> Seems they don't want to reply, probably because they don't have argument.
> Also, the project signs without as anyone to do it, they just did it.
> There is not a vote to say 'The project is agree with this issue'.
>
> At least everyone now
* František Kučera [2019-10-09 16:39]:
> Dne 09. 10. 19 v 19:06 P napsal(a):
> > Stop spamming the list. Thanks.
> >
> If you did not want to start this discussion, you should not have posted
> that statement on the official Guix blog. You could expect what it would do.
>
> Franta
Exactly,
* Wilson Bustos [2019-10-09 17:53]:
> I think even more important,
> When I read that statement I thought every Guix collaborator is in favor of
> that statement,
> or at least a major number of them.
>
> But I get surprise to not find any mail to ask to anyone about this,
> There is not a vote.
* Svante Signell [2019-10-09 13:18]:
> Dear Guix, and other people signing that statement.
> cc: RMS
>
> I do also have problems with your campaign against RMS. Publishing such
> a statement as a blog entry for Guix is very inappropriate. Especially
> in the context of the recent defaming
* Wilson Bustos [2019-10-09 23:54]:
> I think even more important,
> When I read that statement I thought every Guix collaborator is in
> favor of that statement, or at least a major number of them.
And that is exactly what is not being spread on Internet.
I would like to ask those "GNU
* Wilson Bustos [2019-10-09 23:42]:
> Jean Luis,
> Seems they don't want to reply, probably because they don't have
> argument. Also, the project signs without as anyone to do it, they
> just did it. There is not a vote to say 'The project is agree with
> this issue'.
>
> At least everyone
Dne 09. 10. 19 v 23:41 Wilson Bustos napsal(a):
Seems they don't want to reply, probably because they don't have argument.
Also, the project signs without as anyone to do it, they just did it.
There is not a vote to say 'The project is agree with this issue'.
At least everyone now they don't
I think even more important,
When I read that statement I thought every Guix collaborator is in favor of
that statement,
or at least a major number of them.
But I get surprise to not find any mail to ask to anyone about this,
There is not a vote.
Someone just think in that way and use the site
Jean Luis,
Seems they don't want to reply, probably because they don't have argument.
Also, the project signs without as anyone to do it, they just did it.
There is not a vote to say 'The project is agree with this issue'.
At least everyone now they don't want to discuss this.
Don't waste your
Dne 09. 10. 19 v 19:06 P napsal(a):
Stop spamming the list. Thanks.
If you did not want to start this discussion, you should not have posted
that statement on the official Guix blog. You could expect what it would do.
Franta
Dear Guix, and other people signing that statement.
cc: RMS
I do also have problems with your campaign against RMS. Publishing such
a statement as a blog entry for Guix is very inappropriate. Especially
in the context of the recent defaming campaign on him personally on
social media, making him
‐‐‐ Original Message ‐‐‐
On Wednesday, October 9, 2019 6:25 AM, Jean Louis wrote:
> From:
> Mr. Jean Louis
> Nagpur, India
> Day 3 of week 41 of 2019
>
> Hello there,
Stop spamming the list. Thanks.
From:
Mr. Jean Louis
Nagpur, India
Day 3 of week 41 of 2019
Hello there,
I have seen your signature here:
https://guix.gnu.org/blog/2019/joint-statement-on-the-gnu-project/
My opinion on your signing of that defamatory, harassing, biased and
fact-less statement is here:
From:
Mr. Jean Louis
Nagpur, India
Day 3 of week 41 of 2019
Hello there,
I have seen your signature here:
https://guix.gnu.org/blog/2019/joint-statement-on-the-gnu-project/
My opinion on your signing of that defamatory, harassing, biased and
fact-less statement is here:
From:
Mr. Jean Louis
Nagpur, India
Day 3 of week 41 of 2019
Hello there,
I have seen your signature here:
https://guix.gnu.org/blog/2019/joint-statement-on-the-gnu-project/
My opinion on your signing of that defamatory, harassing, biased and
fact-less statement is here:
From:
Mr. Jean Louis
Nagpur, India
Day 3 of week 41 of 2019
Hello there,
I have seen your signature here:
https://guix.gnu.org/blog/2019/joint-statement-on-the-gnu-project/
My opinion on your signing of that defamatory, harassing, biased and
fact-less statement is here:
From:
Mr. Jean Louis
Nagpur, India
Day 3 of week 41 of 2019
Hello there,
I have seen your signature here:
https://guix.gnu.org/blog/2019/joint-statement-on-the-gnu-project/
My opinion on your signing of that defamatory, harassing, biased and
fact-less statement is here:
change my /etc/config.scm file to include the packages
> that I built in the docker container to provision the system with a
> different kernel. What I can't figure out is how to copy the package over
> in a way that guix system reconfigure can see them just using a USB stick.
>
&
would recommend beginners of
Guix System. I have only seen a few do it and they had many months of
experience.
...
Question 3:
It seems crazy to me that I'm downloading everything over and over. At
the office (where I was playing with this) we have fiber, but right here
we have a terrible
with a
different kernel. What I can't figure out is how to copy the package over
in a way that guix system reconfigure can see them just using a USB stick.
Question 1:
On the docker container, if I do guix archive --recursive --export linux >
linux.nar and then move it over to the nuc, I can successfu
yes, I knew about the I/O operations stuff, I turned my fancy retroPC
on just to check, it is not a laptop, it is a desktop PC. It is has a
monocore Pentium 4 3.2 Ghz, and a Parallel ATA hard drive. Please. do
not say it is fancy anymore, I have just written a post for my blog
about it being fancy
On 2018-12-03 00:39, Laura Lazzati wrote:
1GB of RAM? That is a *lot* :)
I have 2 GB on my 2 day-to-day laptops. 1 with GNOME3 GuixSD and 1 with
Parabola+MATE. Both work fine and I rarely have to wait for other
programs than the really heavy ones (Libreoffice comes to mind).
Oh no! my retroPC
> 1GB of RAM? That is a *lot* :)
> I have 2 GB on my 2 day-to-day laptops. 1 with GNOME3 GuixSD and 1 with
> Parabola+MATE. Both work fine and I rarely have to wait for other
> programs than the really heavy ones (Libreoffice comes to mind).
Oh no! my retroPC is fancy :O and I did not know :) I
On 2018-12-02 16:05, Laura Lazzati wrote:
Hi!
On Sat, Dec 1, 2018 at 2:17 PM Giovanni Biscuolo wrote:
happy birthday retroPC! a teenager :-)
It's not its birthday yet, but thank you ;) I just did a basic
installation, since it only has 1GB of RAM memory. But I love it and
criticizing my
Hi!
On Sat, Dec 1, 2018 at 2:17 PM Giovanni Biscuolo wrote:
> happy birthday retroPC! a teenager :-)
It's not its birthday yet, but thank you ;) I just did a basic
installation, since it only has 1GB of RAM memory. But I love it and
criticizing my retroPC is one of the things people should
Hi Laura,
Laura Lazzati writes:
[...]
> Yesterday I mentioned that I installed GuixSD on bare metal over IRC
> channel, in my retroPC that in December this year will be 13 years old
> :)
happy birthday retroPC! a teenager :-)
[...]
> The example for desktop.scm has the line:
> (device
Hi everyone :)
I have some questions as regards documentation:
Yesterday I mentioned that I installed GuixSD on bare metal over IRC
channel, in my retroPC that in December this year will be 13 years old
:)
I did a basic installation, almost followed the first example in:
Hi Mark,
On Thu, 20 Sep 2018 02:35:27 -0400
Mark H Weaver wrote:
> Speaking of our Rust packages, I have a question: is it intentional that
> 'rust-1.23' is still built using 'rust-bootstrap' and not 'rust-1.22'?
Yes, because I'm not done yet :)
> The reason I ask is that, to m
Hi Danny,
Speaking of our Rust packages, I have a question: is it intentional that
'rust-1.23' is still built using 'rust-bootstrap' and not 'rust-1.22'?
The reason I ask is that, to my delight, there appears to be (almost?)
everything needed for a complete source-only bootstrap chain for recent
Hi Rene,
Rene skribis:
> I'm updating my guix repository in Debian/Hurd with the commit
> 40f5c53d89da266055a1dd6571c380f5c57fe5f9.
> When I run `sudo ./pre-inst-env guix system init doc/os-config-hurd.scm /guix
> --fallback --no-substitutes --no-build-hook` show the error:
>
> `
> Backtrace:
Hello,
I'm updating my guix repository in Debian/Hurd with the commit
40f5c53d89da266055a1dd6571c380f5c57fe5f9.
When I run `sudo ./pre-inst-env guix system init doc/os-config-hurd.scm /guix
--fallback --no-substitutes --no-build-hook` show the error:
`
Backtrace:
10 (primitive-load
Hi!
You've read the exception point correctly:
Using New Moon (=unofficial) branding, you are allowed to do whatever
you wish with your distribution, including reconfiguration, different
home page, etc. Go right ahead!
If you make source code changes, you should also supply your modified
source
t; home page, etc. Go right ahead!
> If you make source code changes, you should also supply your modified
> source code to stay within the requirements of the MPL source code license.
>
> Moonchild.
Alright then. I should've asked this question earlier. Better
late than never.
Thanks fo
Hello licensing team of Pale Moon,
a long time ago I packaged Pale Moon in the Newmoon flavor (or
"brand") for GNU Guix.
I have maintained it in my local set of repositories for some
time now, simply because of your redistribution policies
(http://www.palemoon.org/redist.shtml). It is building
Arun Isaac writes:
> Mark H Weaver writes:
>
>> After we switch to using 'invoke' everywhere, or more precisely, after
>> we arrange to never return #false from any phase or snippet, then
>> there should be one more step before removing the vestigial
Mark H Weaver writes:
> After we switch to using 'invoke' everywhere, or more precisely, after
> we arrange to never return #false from any phase or snippet, then
> there should be one more step before removing the vestigial #true
> returns: we should change the code that calls
On Thu 25 Jan 2018 06:31, Maxim Cournoyer writes:
> Where does this `invoke' comes from? Geiser is unhelpful at finding it,
> and it doesn't seem to be documented in the Guile Reference?
https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00163.html
Andy Wingo writes:
> On Wed 24 Jan 2018 14:28, Mark H Weaver writes:
>
>> Andy Wingo writes:
>>
>>> On Wed 24 Jan 2018 13:06, Mark H Weaver writes:
>>>
+ ;; Install to the right directory
+
problems via exceptions, and that drove the shift
> from system / system* to invoke. In the future world where completion
> means success, it doesn't matter what substitute* returns.
There is also the question what it means for substitute* to fail. Does
it fail when one of the substitution
Andy Wingo writes:
> On Wed 24 Jan 2018 14:28, Mark H Weaver writes:
>
>> Andy Wingo writes:
>>
>>> On Wed 24 Jan 2018 13:06, Mark H Weaver writes:
>>>
+ ;; Install to the right directory
+
On Wed 24 Jan 2018 15:45, Hartmut Goebel writes:
> Am 24.01.2018 um 13:14 schrieb Andy Wingo:
>> On Wed 24 Jan 2018 13:06, Mark H Weaver writes:
>>
>>> + ;; Install to the right directory
>>> + (substitute* '("Makefile"
>>>
On Wed 24 Jan 2018 14:28, Mark H Weaver writes:
> Andy Wingo writes:
>
>> On Wed 24 Jan 2018 13:06, Mark H Weaver writes:
>>
>>> + ;; Install to the right directory
>>> + (substitute* '("Makefile"
>>> +
Am 24.01.2018 um 13:14 schrieb Andy Wingo:
> On Wed 24 Jan 2018 13:06, Mark H Weaver writes:
>
>> + ;; Install to the right directory
>> + (substitute* '("Makefile"
>> +"Qsci/Makefile")
>> +
Hi Andy,
Andy Wingo writes:
> On Wed 24 Jan 2018 13:06, Mark H Weaver writes:
>
>> + ;; Install to the right directory
>> + (substitute* '("Makefile"
>> +"Qsci/Makefile")
>> +
Hi!
On Wed 24 Jan 2018 13:06, Mark H Weaver writes:
> + ;; Install to the right directory
> + (substitute* '("Makefile"
> +"Qsci/Makefile")
> + (("\\$\\(INSTALL_ROOT\\)/gnu/store/[^/]+")
> +
Hi Charlie,
> Do I need to submit a FSF copyright assignment to contribute to a package if
> the package is not copyrighted under the FSF?
Guix does not require FSF copyright assignment. Contributing a package
definition to Guix is not the same as contributing to the upstream
project providing
Charlie,
Charlie Sale wrote on 01/01/18 at 23:03:
> Do I need to submit a FSF copyright assignment to contribute to a package if
> the package is not copyrighted under the FSF?
If by ‘package’ you mean a Guix package recipe, or indeed any part of
the Guix source tree: no. Even pseudonymous
Hello Guix!
I have a questiont that I guess I could have asked a different page, but
I figured that I would actually get a timely response here. Here it is:
Do I need to submit a FSF copyright assignment to contribute to a package if
the package is not copyrighted under the FSF?
Thanks for
, then some rewriting the code maybe to get rid
of the original base I was inspired by, and then add new features.
All of the above as a question posed to you only makes sense if
there is at least one more person up to the task, otherwise I can
just keep doing it low priority outside of Guix.
--
ng0
Andy Wingo writes:
> More concretely... if this is necessary (and I suspect but don't know
> that it is,) probably the easiest thing would be for each package to
> install a copyright file in its output derivations. Then a "guix pack"
> would include them automatically. It
Ludovic Courtès writes:
>> Well, from what I know about copyright, that isn't the licence of glibc,
>> which is the sum of all the licences involved, and you'd have to know
>> how to find them if you didn't just unpack the tarball. With pack
>> output in a lot of cases you don't
On Mon 11 Sep 2017 13:29, Alex Vong writes:
>>> Well, from what I know about copyright, that isn't the licence of glibc,
>>> which is the sum of all the licences involved, and you'd have to know
>>> how to find them if you didn't just unpack the tarball. With pack
>>>
l...@gnu.org (Ludovic Courtès) writes:
> Dave Love skribis:
>
>> Ludovic Courtès writes:
>>
>>> Dave Love skribis:
>>>
Alex Vong writes:
> Based on the above general argument, I think we should list all the
>
Dave Love skribis:
> Ludovic Courtès writes:
>
>> Dave Love skribis:
>>
>>> Alex Vong writes:
>>>
Based on the above general argument, I think we should list all the
licenses instead of just GPLv2+ since it would be
101 - 200 of 330 matches
Mail list logo