From: ludo@gnu.org (Ludovic Courtès)
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
"Clément Lassieur" <clement@lassieur.org>,
"Tatiana Sholokhova" <tanja201396@gmail.com>
Subject: Re: packaging Bootstrap for Cuirass' web interface
Date: Mon, 23 Jul 2018 11:04:18 +0200 [thread overview]
Message-ID: <87pnzetjal.fsf@gnu.org> (raw)
In-Reply-To: <CAE4v=pgoJaXXFRT-9j8va0Fe_sUN8T7=oHFrJYGJfVGByzsbYg@mail.gmail.com> ("Gábor Boskovits"'s message of "Mon, 23 Jul 2018 10:03:40 +0200")
Hi there!
Gábor Boskovits <boskovits@gmail.com> skribis:
> Clément Lassieur <clement@lassieur.org> ezt írta (időpont: 2018. júl. 23.,
> H, 9:48):
>
>> 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?
>>
>>
> I think this is a good idea. However, I think we can go on as is for now,
> and refactor later.
I agree.
Actually I think bundling (a subset of) Bootstrap in Cuirass would be
acceptable because Bootstrap is not the kind of thing usually provided
as a package.
However, bundling should be done in a way that makes it easy to track
where those files come from and to update them. We could either use a
Git submodule, or have clear commit messages that specify the repo and
commit that we used.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-07-23 9:04 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 [this message]
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
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=87pnzetjal.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=boskovits@gmail.com \
--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).