unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, Nils Gillmann <ng0@n0.is>
Subject: Re: a GUIX_PACKAGE_PATH / modules puzzle
Date: Sat, 12 May 2018 19:45:36 +0000	[thread overview]
Message-ID: <20180512194536.qgnxh2jt255bssch@abyayala> (raw)
In-Reply-To: <87k1s9c7lz.fsf@elephly.net>

Ricardo Wurmus transcribed 1.0K bytes:
> 
> Nils Gillmann <ng0@n0.is> writes:
> 
> > Here's what's happening now:
> >
> > I took my perl module which is in "pkgs/lang-perl/perl.scm", which contains our basic perl packages,
> > and moved ( + renamed ) them into (core lang-perl perl) in a new directory.
> >
> > If I run GUIX_PACKAGE_PATH="/home/user/src/core" package -s mc I get results for query "mc".
> > When I run GUIX_PACKAGE_PATH="/home/user/src/core" package --show=perl I get the same message
> > as initially pointed out in the opening post.
> 
> I don’t understand what the problem is.  Your description isn’t very
> clear.  If you cannot post a minimal example it is virtually impossible
> for us to help.

I am not sure if I am allowed to point to my git server here. The single repository
includes no code that is against the Guidelines Guix follows, but there are repositories
on it which don't and which (currently) are still usable with Guix.

In any case I've decided to move the core packages for now back into another repository.

If I encounter this problem again, I'll provide more details.

> I’d also like to suggest asking questions on guile-user when you have
> questions about Guile.

Okay, thanks.

> If you have a file “core/lang-perl/perl.scm” and the module is called
> “(core lang-perl perl)” then you should not have “core” itself on
> GUIX_PACKAGE_PATH but its parent directory.

In my example (pkgs lang-perl perl) itself had the parent directory "pkgs".
I admit, code examples would've made it more clear..

Since we can point to github.com regularly, I think my private server would
not be considered problematic?

> --
> Ricardo

  reply	other threads:[~2018-05-12 19:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 22:39 a GUIX_PACKAGE_PATH / modules puzzle Nils Gillmann
2018-05-03  5:16 ` Chris Marusich
2018-05-03  5:36   ` Nils Gillmann
2018-05-03  7:23     ` Chris Marusich
2018-05-03  8:30       ` Nils Gillmann
2018-05-10 22:27         ` Nils Gillmann
2018-05-10 23:26           ` Nils Gillmann
2018-05-11  7:00             ` Nils Gillmann
2018-05-11  7:19               ` Nils Gillmann
2018-05-12 13:43               ` Ricardo Wurmus
2018-05-12 19:45                 ` Nils Gillmann [this message]
2018-05-13  5:15                   ` Ricardo Wurmus
2018-05-11  7:36   ` Nils Gillmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180512194536.qgnxh2jt255bssch@abyayala \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).