[puppy-devel] Re: SVN for usr_devx.sfs enhancements?

Jonathan Marsden wrote: 
If we're agreed that updating usr_devx.sfs is a priority then should
we set up an SVN repository for co-authoring on it? (This could then
extend to be used for the whole distro)

At this point, I think we'll mostly be packaging existing sources, not
editing them.  How do you see SVN or CVS being used in this kind of a
setup?  I'm expecting more of a little database of packages with the URL
to a canonical source code tarball, and the parameters needed to build
it under Puppy, and (later) to package it into "user" and "devel" pieces
if necessary.  Plus various scripts that use this data to grab tarballs
and package them and run tests against the results.  I'm open to other
approaches, though.  We could keep the set of scripts under shared
version control -- is that what you had in mind?


No, not really...although what you're saying is also needed.

SVN can be used to store a whole filesystem, which is what usr_devx.sfs is.
We can pre-populate with the current usr_devx.sfs & then incrementally patch it - starting with openssl & libexif headers.

We should then have another repository for your compiling & packaging scripts, which I think definitely do need to split out into user & devel lumps. User goes into the main distro, devel goes into usr_devs.sfs.

F

Other related posts: