From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Replacing Bower with "guix environment"
Date: Thu, 30 Apr 2015 10:48:27 +0200 [thread overview]
Message-ID: <87d22m3stg.fsf@gnu.org> (raw)
In-Reply-To: <87tww2i6je.fsf@earlgrey.lan> (Christopher Allan Webber's message of "Sun, 26 Apr 2015 22:12:08 -0500")
Christopher Allan Webber <cwebber@dustycloud.org> skribis:
> - The "hip new way" of doing things is to use Bower. Bower is a
> package manager, but it's made specifically for static assets served
> to the user, such as css files, fonts, javascript like jquery, etc.
> Bower also puts these in an extlib/ or whatever, but it puts them in
> that place *for* you.
Interesting.
(Thinking out lout.)
Just like ‘guix system vm’ returns a script that runs QEMU with the
right arguments, one could imagine generating a script that copies
dependencies in the right place maybe?
(define (make-installer assets)
(gexp->script "copy-assets"
#~(begin
(for-each copy-file '#$@assets)
...)))
(This could/should be turned into a package object so that adding it as
an input would drop it in $PATH.)
The developer would have to explicitly run that script to have the files
copied under extlib/.
Alternately one could generate a script that directly runs some http
server with the right parameters so that it finds CSS files, JS files,
etc.
Does that make sense?
Ludo’.
next prev parent reply other threads:[~2015-04-30 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 3:12 Replacing Bower with "guix environment" Christopher Allan Webber
2015-04-27 11:42 ` David Thompson
2015-04-27 13:15 ` Christopher Allan Webber
2015-04-27 14:11 ` David Thompson
2015-04-30 8:48 ` Ludovic Courtès [this message]
2015-04-30 16:40 ` Christopher Allan Webber
2015-04-30 17:17 ` David Thompson
2015-05-01 4:14 ` Christopher Allan Webber
2015-05-01 14:37 ` Ludovic Courtès
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=87d22m3stg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=guix-devel@gnu.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.
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).