On Wed, 2002-04-17 at 22:45, David Douthitt wrote:
> On 4/17/02 at 8:08 AM, Charles Steinkuehler <[EMAIL PROTECTED]>
> wrote:
> > That doesn't change the fact, however, that I think Mike's
> > trying to migrate binary LRP files into CVS to cut space
> > requirements on the SF site. I think the directory
> > arrangement makes sense for binary packages, but is not a
> > good idea for the actual source code.
>
> The way you describe it, it almost sounds like one is trying to find a
> way to use a CVS server as a pseudo-FTP server for public file access.
> I always thought CVS was for Source Code and for Development Sources,
> etc.
David,
Not exactly. Certain directories in the bin/ tree in our repository
*will export daily* to our /pub directory on the shell server. Note: I'm
already exporting our doc/ tree to /pub/doc when documents are updated.
The bin/ tree in cvs serves the following purposes:
* Tracking of updates (change-log, notes, notification of new files,
etc.) (Note: a ftp repository wont give us any of this.)
* Facilitates developer coordination on package and release/branch
updates.
* Fixes the problem that users are unable to locate files in our
/devel directory on the shell server.
* Fixes the problem of a user trying to use an old package/image
because they're unaware of a newer one.
* Allows us to bring our shell quota in line with SF requirements
(1G hard, 512M allocated, and current usage is 1.3G).
> > It's still going to be hard to find packages, but
> > hopefully, an index page or search engine of some sort can
> > make finding a particular binary package easier.
> > Regardless, browsing through a couple of directories in
> > CVS already seems simpler than browsing to the ??? current
> > directories with LRP files spread throughout the /devel
> > tree...
>
> Ah, but that fix is easy: use links. Separate packages into
> directories based on the "Group:" tag, then create links to each file
> in the appropriate glibc* directory based on the "Glibc:" tag.
>
> Another quick alternative:
>
> cd /home/groups/l/leaf/ftphome
> for i in $(find ../devel -name "*.lrp") ; do \
> ln -sf $i $(basename $i) ; \
> done
If it was this trivial to accomplish it would have been done already. As
I stated above, an ftp directory offers none of the tracking or
coordination capabilities of cvs. Additionally, it doesn't solve the
problem of us exceeding our quota on the SF shell server.
For example, just take a look at the /pub/packages/test.txt. It's a
perfect example of why your proposed solution doesn't work. There are
many old packages that have been updated by another project member, but
the old package remains to confuse our users.
--
Mike Noyes <[EMAIL PROTECTED]>
http://sourceforge.net/users/mhnoyes/
http://leaf-project.org/
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
