From: "Jauhien Piatlicki" <piatlicki@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/g-sorcery:master commit in: /
Date: Thu, 19 Sep 2013 23:21:34 +0000 (UTC) [thread overview]
Message-ID: <1379632881.0065e3d59e0477fba424850d4fe366eb2b8f20c2.jauhien@gentoo> (raw)
commit: 0065e3d59e0477fba424850d4fe366eb2b8f20c2
Author: Jauhien Piatlicki (jauhien) <piatlicki <AT> gmail <DOT> com>
AuthorDate: Thu Sep 19 23:21:21 2013 +0000
Commit: Jauhien Piatlicki <piatlicki <AT> gmail <DOT> com>
CommitDate: Thu Sep 19 23:21:21 2013 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/g-sorcery.git;a=commit;h=0065e3d5
README actualized
---
README.md | 31 ++++++++++++++++++++++++++-----
1 file changed, 26 insertions(+), 5 deletions(-)
diff --git a/README.md b/README.md
index dc8a71a..d3dcf2e 100644
--- a/README.md
+++ b/README.md
@@ -52,7 +52,7 @@ Add `jauhien` overlay: **layman -a jauhien**.
Emerge g-sorcery: **emerge -va g-sorcery**.
-Currently two backends are available: **gs-elpa** and **gs-ctan**.
+Currently 3 backends are available: **gs-elpa**, **gs-pypi** and **gs-ctan**.
Here is an example of using gs-elpa backend.
@@ -60,12 +60,22 @@ There are two ways of using **gs-elpa**:
* use it with **layman**
-In this case all you need to do is install **layman-9999**, **g-sorcery**
-and **gs-elpa**. Then you should just run `layman -L` as
+In this case all you need to do is install **layman-9999** and **g-sorcery**.
+Then you should just run `layman -L` as
root and find an overlay you want. Type of overlay will be
displayed as *g-sorcery*. Then you add this overlay as
usual. It's all you need to do and it's the recommended way of
-using **gs-elpa**.
+using **g-sorcery**.
+
+Using **g-sorcery** with layman you can populate overlay only with packages you want.
+To do so you should add a section named [BACKEND] (BACKEND here is the name of backend used for
+your repo). In this section you can add entries named REPO_packages (REPO here is the name
+of repository you want to add) which are space separated list of packages you need. ebuilds for
+dependencies will be generated automatically if backend supports this possibility.
+
+Note, that some overlays may depend on other overlays, in this case you'll need to add those
+dependencies first.
+
* use it as stand-alone tool
@@ -88,6 +98,17 @@ Emerge any package from it, e.g.
**emerge -va clojure-mode**
+To generate only ebuilds we need such a */etc/g-sorcery/g-sorcery.cfg* file can be used:
+
+```
+[main]
+package_manager=portage
+
+[gs-elpa]
+marmalade_packages = clojure-mode clojurescript-mode
+```
+
+
**Generating user ebuilds in user overlay**
Create new user overlay. Run
@@ -106,6 +127,6 @@ Repositories you can use are gnu-elpa, marmalade and melpa. You can use them
all in one overlay. Note, that if you call **generate-tree** command your overlay
will be wiped and overlay tree for a given repository will be generated. Be careful!
-See man pages of **gs-elpa** and **gs-ctan** for further information.
+See man pages of **gs-elpa**, **gs-pypi** and **gs-ctan** for further information.
If you want to develop a new backend see [developer's instructions](https://github.com/jauhien/g-sorcery/blob/master/docs/developer_instructions.rst).
next reply other threads:[~2013-09-19 23:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 23:21 Jauhien Piatlicki [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-13 19:32 [gentoo-commits] proj/g-sorcery:dev commit in: / Jauhien Piatlicki
2015-09-13 19:32 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki
2015-04-22 7:35 Jauhien Piatlicki
2015-04-20 21:36 [gentoo-commits] proj/g-sorcery:dev " Jauhien Piatlicki
2015-04-22 7:35 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki
2014-09-29 19:38 [gentoo-commits] proj/g-sorcery:dev " Jauhien Piatlicki
2014-09-29 19:39 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki
2014-05-10 2:03 Jauhien Piatlicki
2014-05-10 2:03 Jauhien Piatlicki
2014-03-05 17:58 Jauhien Piatlicki
2013-11-22 17:08 Jauhien Piatlicki
2013-11-22 16:55 [gentoo-commits] proj/g-sorcery:dev " Jauhien Piatlicki
2013-11-22 16:54 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki
2013-11-22 16:42 [gentoo-commits] proj/g-sorcery:dev " Jauhien Piatlicki
2013-11-22 16:42 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki
2013-11-22 16:38 Jauhien Piatlicki
2013-09-19 23:22 Jauhien Piatlicki
2013-09-15 22:38 Jauhien Piatlicki
2013-09-15 14:32 Jauhien Piatlicki
2013-09-05 16:33 Jauhien Piatlicki
2013-08-30 17:00 Jauhien Piatlicki
2013-08-29 23:37 Jauhien Piatlicki
2013-08-29 21:30 Jauhien Piatlicki
2013-08-14 8:31 Jauhien Piatlicki
2013-08-12 0:42 Jauhien Piatlicki
2013-08-12 0:36 Jauhien Piatlicki
2013-08-06 20:16 Jauhien Piatlicki
2013-08-06 20:16 Jauhien Piatlicki
2013-08-05 0:54 Jauhien Piatlicki
2013-08-05 0:46 Jauhien Piatlicki
2013-07-30 19:02 Jauhien Piatlicki
2013-07-26 9:43 Jauhien Piatlicki
2013-07-22 17:10 Jauhien Piatlicki
2013-07-15 0:00 Jauhien Piatlicki
2013-07-14 23:51 Jauhien Piatlicki
2013-07-14 22:53 Jauhien Piatlicki
2013-07-14 1:00 Jauhien Piatlicki
2013-07-13 23:41 Jauhien Piatlicki
2013-07-11 0:09 Jauhien Piatlicki
2013-07-11 0:05 Jauhien Piatlicki
2013-07-02 14:50 Jauhien Piatlicki
2013-07-02 10:21 Jauhien Piatlicki
2013-06-30 19:55 Jauhien Piatlicki
2013-06-20 22:53 Jauhien Piatlicki
2013-06-20 22:53 Jauhien Piatlicki
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=1379632881.0065e3d59e0477fba424850d4fe366eb2b8f20c2.jauhien@gentoo \
--to=piatlicki@gmail.com \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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