SJS wrote:
Where does your organization fit into this scheme? Are you the
consulting client, or is the client consulting with your organizatino?
I am the consultant. My client is paying me to help them out with
getting the distribution they use in their appliances up to date and
establish a better process for managing and releasing it.
I am going to be version controlling all of the SRPM's minus the pristine
source tarballs which never change.
Start with the pristine tarballs. It helps.
Well, perhaps I misspoke above. I will be using the original distro's
SRPM's which contains the pristine tarballs themselves and we won't be.
We just won't be putting them in the VCS or changing them.
I take it free-as-in-beer is an important constraint?
Free-as-in-freedom is an important constraint. :)
Even the CVS folks recommended against using $Revision$ as a product
identifier; embedded keywords are for reconstructing source from
binaries.
For product-level version-control, you should have a "version" file that
your release process updates, commits, and embeds into your product.
A version file is a good idea. They keywords aren't really a big deal.
Not so silly, just move the "repository" one level down.
Hmm...
cd /etc
hg init
scp [EMAIL PROTECTED]:/repo/default.hgignore .hgignore
What's in the .hgignore?
hg add sudoers
hg commit sudoers
Ok, so the hg init above and these two commands adds sudoers to the
local hg repository on the local machine...
ssh [EMAIL PROTECTED]
mkdir /repo/hosts/hostname
cd /repo/hosts/hostname
hg clone ssh://[EMAIL PROTECTED]:/etc
And here we create the repo on our main hg host and then clone the local
repository we created back to the main hg host?
I am finding that putting my config files under version control is great
for backup purposes also. Just the other day I accidentally deleted a
couple of config files which I normally keep under version control but
in this case they weren't and it was a real hassle to recreate them.
I am liking more and more the ability to make changes, run things for a
while and see if the change had the effect I want and if so commit and
if not revert.
Keep your pro/con notes so you can give us the chain of reasoning for
your decsion.
I think I will just have to play with Hg and see if it works like I
want. But I think I should really have a decision made by Monday so I'm
not sure I'm going to really have many notes to share. And of all of the
posts on this thread so far few have really contained information useful
to me, this post of yours (as probably the only person on the list who
has used hg) being an exception. :)
--
Tracy R Reed Read my blog at http://ultraviolet.org
Key fingerprint = D4A8 4860 535C ABF8 BA97 25A6 F4F2 1829 9615 02AD
Non-GPG signed mail gets read only if I can find it among the spam.
--
KPLUG-List@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
