From: Chris Marusich <cmmarusich@gmail.com>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel@gnu.org, "Clément Lassieur" <clement@lassieur.org>,
"Tatiana Sholokhova" <tanja201396@gmail.com>
Subject: Re: packaging Bootstrap for Cuirass' web interface
Date: Fri, 27 Jul 2018 01:41:21 -0700 [thread overview]
Message-ID: <87va91rrym.fsf@gmail.com> (raw)
In-Reply-To: <20180723113142.33c9cdbe@alma-ubu> ("Björn Höfling"'s message of "Mon, 23 Jul 2018 11:31:42 +0200")
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> writes:
> On Mon, 23 Jul 2018 09:48:15 +0200
> Clément Lassieur <clement@lassieur.org> wrote:
>
>> Hello!
>>
>> We are going to embed Bootstrap files to our Cuirass service.
>> Wouldn't it be better to package Bootstrap and get the service to use
>> the package directly? I think it would make maintenance easier, and
>> I'm unsure it's good to have huge files on which we don't have
>> control in our Cuirass git repository. WDYT?
>>
>> Clément
>
> Building from "source" would be cool, but looks like a lot of "fun":
>
> https://getbootstrap.com/docs/4.0/getting-started/build-tools/#tooling-setup
>
> Here is the npm build script. Look at the dev-dependencies:
>
> https://github.com/twbs/bootstrap/blob/v4.0.0-beta.2/package.json
>
> NPM-Yogurt.
>
> I think the only change to go from sources is write your own simple
> build scripts and call your own SASS-compiler and JS minifier.
See also:
http://dustycloud.org/blog/javascript-packaging-dystopia/
"Let's Package jQuery: A Javascript Packaging Dystopian Novella"
by Christopher Webber. jQuery also appears to be a dependency of
Bootstrap (listed under Bootstrap's "peerDependencies").
It's quite a large Gordian knot. I hope we can cut it someday!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-07-27 8:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 7:48 packaging Bootstrap for Cuirass' web interface Clément Lassieur
2018-07-23 8:03 ` Gábor Boskovits
2018-07-23 9:04 ` Ludovic Courtès
2018-07-23 11:29 ` Clément Lassieur
2018-07-24 20:29 ` Tatiana Sholokhova
2018-07-24 23:39 ` Clément Lassieur
2018-07-25 8:10 ` Clément Lassieur
2018-07-25 8:46 ` Clément Lassieur
2018-07-25 9:18 ` Clément Lassieur
2018-07-25 10:05 ` Gábor Boskovits
2018-07-25 10:16 ` Clément Lassieur
2018-07-26 9:07 ` Clément Lassieur
2018-07-26 13:41 ` Ludovic Courtès
2018-07-27 1:43 ` Clément Lassieur
2018-07-27 8:50 ` Ludovic Courtès
2018-07-27 10:18 ` Clément Lassieur
2018-07-27 17:43 ` Clément Lassieur
2018-07-29 16:54 ` Ludovic Courtès
2018-07-26 13:39 ` Ludovic Courtès
2018-07-29 23:45 ` Clément Lassieur
2018-07-26 13:42 ` Ludovic Courtès
2018-07-23 9:31 ` Björn Höfling
2018-07-23 11:18 ` Clément Lassieur
2018-07-27 8:41 ` Chris Marusich [this message]
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=87va91rrym.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=tanja201396@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.
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).