From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-devhelp@lists.gentoo.org
Cc: Stayvoid <stayvoid@gmail.com>
Subject: Re: [gentoo-devhelp] CLFSWM.ebuild
Date: Fri, 13 Jan 2012 17:38:22 +0100 [thread overview]
Message-ID: <4F105DFE.8040307@gentoo.org> (raw)
In-Reply-To: <CAK5fS_G8aiBXE=f3XX_jo1BL0acjAZoguH01hPnv=ab-CvCdTw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
Stayvoid schrieb:
> Hello!
>
> I am trying to write a ebuild for CLFSWM: http://common-lisp.net/project/clfswm/
>
> It's hard because I don't know bash and lisp.
>
> Here is what I have for today:
> http://paste.pocoo.org/show/533700/
>
> I've successfully run: manifest, configure, compile, install and
> merge. What should I do next? How to check that it's OK?
> Is there some guide for "checking" ebuilds?
>
> I've also tried to run it via dev-lisp/clisp, but it failed. (I've
> installed clisp manually (via emerge). I've thought that it should be
> done automatically (via ebuild).) And I'm
> not sure why.
> Here is a guide: http://trac.common-lisp.net/clfswm/wiki/Setup
>
>
> Cheers.
>
>
I dont know lisp myself, but beside the lisp specific configure opts
(which i cannot comment on, since i dont know them) the ebuild looks ok.
Why did you use the ebuild command to install this package? Just create
it in your local overlay and you can use emerge to install the package.
That additionally has the advantage, that the dependencies (like clisp)
will be installed, the ebuild command alone does not do any dependency
related work.
If you want to check, what it installs, you can either use emerge with
--verbose switch or tools like equery (from gentoolkit package) to view
the list of installed files.
> I've also tried to run it via dev-lisp/clisp, but it failed.
I dont know, what you mean with this sentence, so if there is still
something left/open for a question, then i suggest you rephrase it and
post again on this list. As alternative, you could also ask on IRC in
channels like #gentoo-dev-help or #gentoo-sunrise on freenode network.
--
Thomas Sachau
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 380 bytes --]
next prev parent reply other threads:[~2012-01-13 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 20:50 [gentoo-devhelp] CLFSWM.ebuild Stayvoid
2012-01-13 16:38 ` Thomas Sachau [this message]
2012-01-14 4:12 ` Stayvoid
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F105DFE.8040307@gentoo.org \
--to=tommy@gentoo.org \
--cc=gentoo-devhelp@lists.gentoo.org \
--cc=stayvoid@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox