Re: Mobile source location

blmblm@xxxxxxxxxxxxx wrote:

Great questions.
Clearly some things in this scheme just cry out for real version
control. What I'm unsure about is how well that would mesh with my
current scheme of keeping code with other related files. It may be
significant that for most of what I do, there are apt to be more of
those other files (usually documents of various sorts) than code.

I version-control documents, too.

In writing my earlier post I was also thinking of a CVS repository
as something without the ability to group related bunches of code
in any way other than "different versions of the same program".
That could well be wrong.

It is wrong. CVS catalogs can relate all your projects to each other in a way that allows multiple projects to share code that is controlled in its own little piece. You can inter-relate CVS projects at the server.

I guess what I'm thinking is that someone with a few large projects
might have different needs from someone with many small projects.
Maybe not.

Maybe so, but version control serves both sets of needs.

So why put your repository in /opt, which I think of as being
files not owned by anyone (other than root) ....

In my case, /opt/cvsrepo is owned by a fictitious developer owner. The individual projects are owned by individuals, but the repository itself is a system resource.

You can use /var or /opt or /usr, or their .../local variants, for the repository. I just wouldn't put it under /home/anyone.

Again, the repository is owned by a common owner; only the projects are owned by their owners.

By the way, I didn't intend to make a "work versus home"
distinction; on all the systems where I control what goes where,
the only things that go in "system" directories are things I
don't associate with a particular owner. This may be a result

Like a version-control repository. It is not associated with a particular owner either, other than the fake user that is used so I don't risk things being SUID root.

of my having spent my formative years in mainframe environments,
in which I didn't have administrator privileges on most of the
systems I used.

Ditto CVS. Just belong to the same group as the CVS repository owner.

A version-control repository is shared by the system's users, not dedicated to any one (real) user.

It wouldn't be much use otherwise, would it?

--
Lew
.

Relevant Pages

  • Re: Mobile source location
    ... What I'm unsure about is how well that would mesh with my ... current scheme of keeping code with other related files. ... but version control serves both sets of needs. ... would have his/her own repository for code he/she owns, ...
    (comp.lang.java.programmer)
  • Re: Mobile source location
    ... CVS repository, the repository could get pretty cluttered. ... control; it could be I just need to do some reading up and figure ... of little bunches of code, ...
    (comp.lang.java.programmer)
  • Re: Some questions about INTRACTIVECHANGE Event.
    ... leaves the control. ... OWNER_ TEXT. ... For example, as a user types in a text box, the InteractiveChange ... A KeyPress event is useful for intercepting keystrokes entered in a ...
    (microsoft.public.fox.helpwanted)
  • RE: [Full-disclosure] RE: [ISN] How To Save The Internet
    ... The point might be better made here that we have many security models ... a box owner may assign so that their access permissions are granted ... the current legal morass over intellectual property is of social value ... Nor is there much up-front discussion for consumers of what they can control, ...
    (Full-Disclosure)
  • Re: Mobile source location
    ... source code that I might at some point want to interact with via ... CVS repository, the repository could get pretty cluttered. ... Version control provides a single point of interaction for all the projects which need all those little pieces. ... You express the various needs for source code management that version control systems exist to serve. ...
    (comp.lang.java.programmer)