[Rule-list] cvs directory hierarchy

[Chuck Moss]

On Sun, Feb 24, 2002 at 09:01:20PM -0800, James wrote:
> On Sun, 24 Feb 2002 23:49:47 -0500
> Chuck Moss <cmrule at mossc.com> wrote:
> 
> > I would like to go ahead and get some code/docs/etc into cvs.
> > In preparation for that we need to start setting up the directory tree.
> > 
> > For lack of a better idea here are the subdirectories I would suggest
> > setting up:
> > installer
> > docs
> > contrib
> > 
> > 
> > Is this adequate or should we create a more standard "src" subdirectory
> > with an installer subdirectory under that?
> > 
> > Any other suggestions? (PLEASE)  I know the original directory tree is
> an
> > important decision to keep organized but I don't have a real good feel
> for
> > what code will end up part of the whole project as yet.
> > 
> > Chuck
> 
> If I may.  More of a question than a suggestion, but could a "base"
> anaconda src.rpm or tarball be put into cvs.  It can be checked out but
> not modified.  This I would hope would make sure that there is always an
> ultimate rollback point.

I was actually thinking that we would probably want to "import" the stock
anaconda then make changes to that.
We can always check out any VERSION of the code from that point forward.


Chuck


> > 
> > 
> > 
> > _______________________________________________
> > Rule-list mailing list
> > Rule-list at mail.freesoftware.fsf.org
> > http://mail.freesoftware.fsf.org/mailman/listinfo/rule-list
> 
> _______________________________________________
> Rule-list mailing list
> Rule-list at mail.freesoftware.fsf.org
> http://mail.freesoftware.fsf.org/mailman/listinfo/rule-list

_______________________________________________
Rule-list mailing list
Rule-list at mail.freesoftware.fsf.org
http://mail.freesoftware.fsf.org/mailman/listinfo/rule-list