From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: packaging Bootstrap for Cuirass' web interface Date: Mon, 23 Jul 2018 10:03:40 +0200 Message-ID: References: <87zhyitmtc.fsf@lassieur.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000000b5a110571a6163d" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40822) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fhVov-0005L7-Qp for guix-devel@gnu.org; Mon, 23 Jul 2018 04:03:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fhVou-0001Jn-TS for guix-devel@gnu.org; Mon, 23 Jul 2018 04:03:53 -0400 Received: from mail-io0-x232.google.com ([2607:f8b0:4001:c06::232]:44192) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fhVou-0001JW-OE for guix-devel@gnu.org; Mon, 23 Jul 2018 04:03:52 -0400 Received: by mail-io0-x232.google.com with SMTP id q19-v6so14797380ioh.11 for ; Mon, 23 Jul 2018 01:03:52 -0700 (PDT) In-Reply-To: <87zhyitmtc.fsf@lassieur.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?UTF-8?Q?Cl=C3=A9ment_Lassieur?= Cc: Guix-devel , Tatiana Sholokhova --0000000000000b5a110571a6163d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cl=C3=A9ment Lassieur ezt =C3=ADrta (id=C5=91pont: 2= 018. j=C3=BAl. 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 don't know how much effort would this involve. Having a minimal subset of Bootstrap that is currently needed for Cuirass can be done easily I guess, but that is not usually we package things. Packaging Bootstrap with all the bells and whistles seems like a big effort. WDYT? We could also make this minimal package not publicly visible, if we go this way. > Cl=C3=A9ment > --0000000000000b5a110571a6163d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=
Hello!

We are going to embed Bootstrap files to our Cuirass service.=C2=A0 Wouldn&= #39;t
it be better to package Bootstrap and get the service to use the package directly?=C2=A0 I think it would make maintenance easier, and I'm unsur= e it's
good to have huge files on which we don't have control in our Cuirass git repository.=C2=A0 WDYT?


I think this is a good idea. However, = I think we can go on as is for now, and refactor later. I don't know ho= w much effort
would this involve. Having a minimal subset of Boot= strap that is currently needed for Cuirass can be done easily I guess, but = that is not usually we package things.
Packaging Bootstrap with a= ll the bells and whistles seems like a big effort. WDYT? We could also make= this minimal package not publicly visible, if we go this way.=C2=A0
<= div>=C2=A0
Cl=C3=A9ment
--0000000000000b5a110571a6163d--