From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Cl=C3=A9ment?= Lassieur Subject: Re: packaging Bootstrap for Cuirass' web interface Date: Mon, 23 Jul 2018 13:29:23 +0200 Message-ID: <87wotmtcks.fsf@lassieur.org> References: <87zhyitmtc.fsf@lassieur.org> <87pnzetjal.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51512) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fhZ1t-0005VW-IV for guix-devel@gnu.org; Mon, 23 Jul 2018 07:29:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fhZ1q-0002ff-Aw for guix-devel@gnu.org; Mon, 23 Jul 2018 07:29:29 -0400 In-reply-to: <87pnzetjal.fsf@gnu.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: Ludovic =?utf-8?Q?Court=C3=A8s?= , Tatiana Sholokhova Cc: Guix-devel Ludovic Court=C3=A8s writes: > Hi there! > > G=C3=A1bor Boskovits skribis: > >> Cl=C3=A9ment Lassieur ezt =C3=ADrta (id=C5=91pont= : 2018. 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 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. Understood. I prefer clear commit messages to submodules :-) Tatiana, could you please add the version and the repo link to the commit message that adds static files? The idea is that people should be able to update it easily. If there is anything special, any kind of complicated procedure, that we need to follow in order to upgrade Bootstrap, could you write it in a README? But I imagine it should be fairly simple. Thank you, Cl=C3=A9ment