Can't commit any changes?

[Ray Bartlett]

Gosh, Mike, thanks for taking the time to write.  I had already found
that page but clearly my definition of "simple" isn't at all matching
the Mercurial concept.  In the "quick start" I saw that you clone via
http...didn't realize that didn't allow for the full circle to happen.

Really, I need a simple step by step walk-through (if there is such a
thing) for setting up a repository that people can write and read to.
I'm not sure why it matters whether it's /usr/var/www/html or
/some/other/directory.  Users are hoping to use a Mac client called Hg
(a gui) to do most of the work.

How exactly does one return a cloned repo back to the pool so others
can find it, access it, and make new changes?

In our case, our developers want to be able to quickly and immediately
see how the changes look on the web, hence the need to publish to the
/var/www/html directory.

Is there a syntax so that instead of "publishing by http" they can
publish some other fashion?  Does Mercurial usually require people be
on the same local machine?  If so, it seems kind of impractical.

Again, thank you for the help.  I guess coming from a mindset of FTP
or so on, I feel like it should be a relatively easy thing to use
Mercurial over a intranet or the internet.  I need people to be able
to be home and still able to clone, make changes, and return their
files back to the pool.

Am I just barking up the wrong tree entirely?  Is this what Mercurial
does?  Or should I investigate other version control options?  Or just
tell people they need the command line and they have to ssh directly
into the /var/www/html directory to do any work?



On Tue, Jan 11, 2011 at 4:46 PM, Mike Crowe <drmikecrowe at gmail.com> wrote:
> Ray,
> Couple of things.  By seeing /web/root, it appears you are using a
> web-server in some fashion to serve the repo's.  Make sure to check your
> method and insure it supports pushing (what each developer will use to send
> their committed changes back to the repo).
>  Check http://mercurial.selenic.com/wiki/PublishingRepositories to see how
> your method will react.
> You *may* want to consider setting up something like this:
>  http://dev.lshift.net/paul/mercurial-server/docbook.html
> Just my 2c.
> Mike
> On Tue, Jan 11, 2011 at 4:36 PM, Ray Bartlett <rbartlett at 20miletech.com>
> wrote:
>>
>> I'm so sorry if this is a common issue -- I'm a newbie to any kind of
>> version control and have (I think!) gotten most of the way there.  I'm
>> the sysadmin in a small office with a Linux dev server  and users on
>> Macs.
>>
>> I've set up some repositories that can be cloned.  People seem to be
>> getting no errors when they make changes, and their local individual
>> files are changed.
>>
>> However, I'm unable to figure out why it's impossible for changes to
>> be committed back to the repository.
>>
>> Can Mercurial even do this?  :-)
>>
>> Is this a permission problem?  I tried "chmod 777 -R /web/root" and it
>> didn't help.
>>
>> I need a version control model where people can clone a central copy
>> of something, work on it, and then recommit it with their changes so
>> other people can use the most recent version.  If this isn't how
>> Mercurial works, I guess I need to look elsewhere.
>>
>> Again, apologies, but since everyone in the office (including me!) is
>> totally new to version control, any and all help is greatly
>> appreciated.
>>
>> Thanks very much.
>> _______________________________________________
>> Mercurial mailing list
>> Mercurial at selenic.com
>> http://selenic.com/mailman/listinfo/mercurial
>
>