* Packing software developed in GNU Guile Scheme @ 2016-05-12 15:28 Daniel Pimentel 2016-05-12 19:16 ` Amirouche Boubekki 2016-05-16 14:20 ` Christopher Allan Webber 0 siblings, 2 replies; 6+ messages in thread From: Daniel Pimentel @ 2016-05-12 15:28 UTC (permalink / raw) To: guile-devel Hi Guiles, I developed a software with GNU Guile Scheme and I'd like packing to distribute it. How do I do? Using Makefile? Project dependences: Guile, LSH/SSH. Thanks and sorry for my newbie's question :) Note: I'll packing for Guix/GuixSD in soon, but I'd like to distribute to other distribution by tarball for example. -- Daniel Pimentel (d4n1) ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Packing software developed in GNU Guile Scheme 2016-05-12 15:28 Packing software developed in GNU Guile Scheme Daniel Pimentel @ 2016-05-12 19:16 ` Amirouche Boubekki 2016-05-12 20:36 ` David Pirotte 2016-05-16 14:20 ` Christopher Allan Webber 1 sibling, 1 reply; 6+ messages in thread From: Amirouche Boubekki @ 2016-05-12 19:16 UTC (permalink / raw) To: Daniel Pimentel, Guile User; +Cc: guile-devel, guile-devel [-- Attachment #1: Type: text/plain, Size: 3294 bytes --] Héllo Daniel! On 2016-05-12 17:28, Daniel Pimentel wrote: > Hi Guiles, > > I developed a software with GNU Guile Scheme and I'd like packing to > distribute it. > > How do I do? Using Makefile? > > Project dependences: Guile, LSH/SSH. I personally just spell everything inside a directory. But there is really no way to install the things. I just explain how to run my program in-place and usually it's good enough, for people to get interested (or not!). If someone feel like adding autotools or guix, they can feel free to do it. That being said, I am bit a liar because the modules I use nowdays feet in a single file. You can install them just copy/paste without forgetting denpendencies along the way... GUILE_LOAD_PATH is, most of the time, when I run algorithms local to the current directory and some global directory. I do so using the `L` (for *L*oadpath ) with `guile' command, say `guile -L . uav.scm' [1] for instance will start uav database server on my machine. [1] PS: where `.' means current directory. Instead of period, you can use `pwd`. The content of the directory of the search engine is given by the `tree' command is: ``` . ├── COPYING ├── db │ ├── tuples_index.wti │ ├── tuples.wt │ ├── WiredTiger │ ├── WiredTiger.basecfg │ ├── WiredTiger.lock │ ├── WiredTigerLog.0000000001 │ ├── WiredTigerLog.0000000002 │ ├── WiredTigerPreplog.0000000002 │ ├── WiredTiger.turtle │ └── WiredTiger.wt ├── debug.scm ├── htmlprag.scm ├── https-get.scm ├── hyper-port.scm ├── hyper.scm ├── hyper-server.scm ├── hyper-worker.scm ├── minikanren.scm ├── README.md ├── stopwords.en.txt ├── TODO ├── uav.scm ├── wiredtiger.scm └── wiredtigerz.scm 1 directory, 25 files ``` Here is the number of lines of every file I've written for this project including dependencies: ``` 4 hyper-port.scm 196 hyper.scm 5 hyper-server.scm 29 hyper-worker.scm 339 minikanren.scm 271 uav.scm 637 wiredtiger.scm 681 wiredtigerz.scm ``` From my experience, this scheme can be used any pure module system, even so with guile bytevectors which support several schemes. I feel like packaging would be overrated on my project. Also professional experience tells me programs are much bigger (at least in Python). At $WORK, I dealt with a single class over more that ten thousand lines of code split over two files. In comparison two thousand (at the very least!) blobs of parens over nine files seems hideous b/c file very small in personal projects. > > Thanks and sorry for my newbie's question :) > It's not, there is different way to do it. Mind the fact that this is written (somewhere (over the ra1nybow)) that Facebook and google have massive repositories. Those are not databases of user data, but there source code is in single tarball. That would be 500 000 000 lines of code by the standard of my $WORK. > > Note: I'll packing for Guix/GuixSD in soon, but I'd like to distribute > to other distribution by tarball for example. Thanks in advance! -- Amirouche ~ amz3 ~ http://www.hyper(or dev.fr move.net) [-- Attachment #2: Capture d'écran de 2015-11-01 20-25-10.png --] [-- Type: image/png, Size: 1933554 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Packing software developed in GNU Guile Scheme 2016-05-12 19:16 ` Amirouche Boubekki @ 2016-05-12 20:36 ` David Pirotte 0 siblings, 0 replies; 6+ messages in thread From: David Pirotte @ 2016-05-12 20:36 UTC (permalink / raw) To: Amirouche Boubekki; +Cc: Guile User, guile-devel [-- Attachment #1: Type: text/plain, Size: 184 bytes --] Amirouche, Hello, > Le Thu, 12 May 2016 21:16:50 +0200, > Amirouche Boubekki <amirouche@hypermove.net> a écrit : Please don't attach images to your emails! Thanks, David [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 473 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Packing software developed in GNU Guile Scheme 2016-05-12 15:28 Packing software developed in GNU Guile Scheme Daniel Pimentel 2016-05-12 19:16 ` Amirouche Boubekki @ 2016-05-16 14:20 ` Christopher Allan Webber 2016-05-16 15:59 ` Daniel Pimentel 1 sibling, 1 reply; 6+ messages in thread From: Christopher Allan Webber @ 2016-05-16 14:20 UTC (permalink / raw) To: Daniel Pimentel; +Cc: guile-devel Daniel Pimentel writes: > Hi Guiles, > > I developed a software with GNU Guile Scheme and I'd like packing to > distribute it. > > How do I do? Using Makefile? Maybe look at the automake files from Sly or Guix. > Project dependences: Guile, LSH/SSH. > > Thanks and sorry for my newbie's question :) > > Note: I'll packing for Guix/GuixSD in soon, but I'd like to distribute > to other distribution by tarball for example. No worries! Yes, it needs to be better documented. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Packing software developed in GNU Guile Scheme 2016-05-16 14:20 ` Christopher Allan Webber @ 2016-05-16 15:59 ` Daniel Pimentel 2016-05-16 17:31 ` David Pirotte 0 siblings, 1 reply; 6+ messages in thread From: Daniel Pimentel @ 2016-05-16 15:59 UTC (permalink / raw) To: Christopher Allan Webber; +Cc: guile-devel > Maybe look at the automake files from Sly or Guix. I was using a Automake, but without success because I never use it with GNU Guile Scheme (only in C/C++ projects) but I'll use Guix to packing it. Thanks, ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Packing software developed in GNU Guile Scheme 2016-05-16 15:59 ` Daniel Pimentel @ 2016-05-16 17:31 ` David Pirotte 0 siblings, 0 replies; 6+ messages in thread From: David Pirotte @ 2016-05-16 17:31 UTC (permalink / raw) To: Daniel Pimentel; +Cc: guile-devel [-- Attachment #1: Type: text/plain, Size: 663 bytes --] Hi Daniel, > > Maybe look at the automake files from Sly or Guix. > > I was using a Automake, but without success because I never use it with > GNU Guile Scheme (only in C/C++ projects) but I'll use Guix to packing > it. There is GNU Foliot [1], fully written in Guile, fully autotool chained, a good example as well, not because I wrote it :) but because it also includes a user script written in guile of course, which needs not be compiled and installed in $prefix/bin, files are here [2] I'd be happy to help, ping me... Cheers, David [1] http://www.gnu.org/software/foliot/ [2] http://git.savannah.gnu.org/cgit/foliot.git/tree/ [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 473 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-05-16 17:31 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2016-05-12 15:28 Packing software developed in GNU Guile Scheme Daniel Pimentel 2016-05-12 19:16 ` Amirouche Boubekki 2016-05-12 20:36 ` David Pirotte 2016-05-16 14:20 ` Christopher Allan Webber 2016-05-16 15:59 ` Daniel Pimentel 2016-05-16 17:31 ` David Pirotte
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).