git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git for change control of software deployment updates

From
NKNeal Kreitzinger <nkreitzinger@gmail.com>
Date
Dec 11, 2011, 05:09 UTC
Message-ID
<jc1dur$80q$1@dough.gmane.org>
In-Reply-To
<CAJDDKr7+GeJTR986DSqKpQRWsXGFVzjBqg6WgRyG-EtycrQs7A@mail.gmail.com>
On 12/10/2011 9:19 PM, David Aguilar wrote:
Show 15 quoted lines
> On Fri, Dec 9, 2011 at 6:37 PM, Neal Kreitzinger<neal@rsss.com>  wrote:
>> I am considering using git with submodules to deploy most of our updates to
>> our customer linux servers (not including third party rpm updates already
>> tracked by linux distro rpm repository).  Has anyone else done this?
>> Comments?  (Sanity check.)  (I am new to submodules.)
>
> I wrote a script that converts a git source repository into a redhat
> src.rpm.  We use it at my $dayjob.  How about doing something like
> that?  After you have a src.rpm you can create rpms that you can
> distribute using yum.  You are already using rpm which is why I
> mention it.  Converting a directory of rpm files into a hostable
> repository is as simple as `createrepo /path/to/rpms/`.
>
> The git project has a 'make rpm' target in its Makefile that you could
> use as an example.

We use rhel so, yes, we use the redhat repo to get rhel patches. Is that what you mean by "You are already using rpm"? (We do not write our own rpm's at this time.)

v/r, neal

Previous: David Aguilar
Message 3 of 3 in “git for change control of software deployment updates”
  1. Neal KreitzingerDec 10, 2011
  2. David AguilarDec 11, 2011
  3. Neal KreitzingerDec 11, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.