Hi all!
I am going to build and maintain RPM of puredata for ALT Linux. It uses git for building RPM packages so I want to pull from existing RCS (git preferrably) repositories of pd-vanilla and pd-extended if any.
So my question is:
Is there a working git repository of pd-vanilla and/or pd-extended or is the development held in SVN or such? Found only tarball of git repository on Miller Puckette's page (which obviously not exactly what I need) but no other links to git repositories.
Thanks for any advice in advance.
Timur Batyrshin wrote:
Hi all!
I am going to build and maintain RPM of puredata for ALT Linux. It uses git for building RPM packages so I want to pull from existing RCS (git preferrably) repositories of pd-vanilla and pd-extended if any.
So my question is:
Is there a working git repository of pd-vanilla and/or pd-extended or is the development held in SVN or such? Found only tarball of git repository on Miller Puckette's page (which obviously not exactly what I need) but no other links to git repositories.
the public repository for Pd (Pd-vanilla, externals, Pd-extended,...) is subversion: https://pure-data.svn.sourceforge.net/svnroot/pure-data
miller privately uses git for developing Pd, and checks in the changes at every milestone (or so).
so far, you cannot pull Pd via git (unless you install git-svn :-))
fgmasdr IOhannes
I don't know offhand how much trouble it would be to set up a git repository on sourceforge, but if it were there I'd be happy to keep it in sync with mine.
cheers Miller
On Sat, May 16, 2009 at 05:15:43PM +0200, IOhannes m zmoelnig wrote:
Timur Batyrshin wrote:
Hi all!
I am going to build and maintain RPM of puredata for ALT Linux. It uses git for building RPM packages so I want to pull from existing RCS (git preferrably) repositories of pd-vanilla and pd-extended if any.
So my question is:
Is there a working git repository of pd-vanilla and/or pd-extended or is the development held in SVN or such? Found only tarball of git repository on Miller Puckette's page (which obviously not exactly what I need) but no other links to git repositories.
the public repository for Pd (Pd-vanilla, externals, Pd-extended,...) is subversion: https://pure-data.svn.sourceforge.net/svnroot/pure-data
miller privately uses git for developing Pd, and checks in the changes at every milestone (or so).
so far, you cannot pull Pd via git (unless you install git-svn :-))
fgmasdr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sat, May 16, 2009 at 12:28:01PM -0700, Miller Puckette wrote:
I don't know offhand how much trouble it would be to set up a git repository on sourceforge, but if it were there I'd be happy to keep it in sync with mine.
Hi Miller,
Isn't it a feature of distributed version control systems like git that you can push/clone a copy of your branch to a web location? I know this is true of bzr, where I can just go: bzr push stfp://mccormick.cx/www/blah/ - I am sure there is something similar for git (I think it's "clone") and then you could keep your repo synced directly on the Pd download page. This would make it much nicer for those of us who want to branch and hack on Pd's source code, and would also make it much easier to contribute patches against cutting edge Pd, back to you.
Best,
Chris.
В Sat, 16 May 2009 12:28:01 -0700 Miller Puckette mpuckett@imusic1.ucsd.edu пишет:
I don't know offhand how much trouble it would be to set up a git repository on sourceforge, but if it were there I'd be happy to keep it in sync with mine.
To let others pull from your git repository you can simply put it on HTTP or FTP or such without packing it into a tarball. People would not be able to browse it but will be able to pull commits from it.
Ok... I put it up on http://crca.ucsd.edu/~msp/Software/pd-git/ - I can't imagine this would work too well since the git repository mostly consists of a single compressed 4M file, which presumably your git client has to download wholesale. But if it functions for you (or if you can suggest a way I could do it better) that's easy for me to maintain :)
Miller
On Sun, May 17, 2009 at 08:36:35PM +0400, Timur Batyrshin wrote:
?? Sat, 16 May 2009 12:28:01 -0700 Miller Puckette mpuckett@imusic1.ucsd.edu ??????????:
I don't know offhand how much trouble it would be to set up a git repository on sourceforge, but if it were there I'd be happy to keep it in sync with mine.
To let others pull from your git repository you can simply put it on HTTP or FTP or such without packing it into a tarball. People would not be able to browse it but will be able to pull commits from it.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sun, 17 May 2009 11:10:46 -0700 Miller Puckette wrote:
Ok... I put it up on http://crca.ucsd.edu/~msp/Software/pd-git/ - I can't imagine this would work too well since the git repository mostly consists of a single compressed 4M file, which presumably your git client has to download wholesale.
I think it is because of git-repack or such.
But if it functions for you (or if you can suggest a way I could do it better) that's easy for me to maintain :)
Actually you should not copy but push your working repository to your public one.
Something like:
Set up the public repository on the web server: mkdir ~msp/Software/pd/ cd ~msp/Software/pd/ git-init
Add remote to your working repository on your working computer: cd path/to/git/repo/pd/ git remote add pubrepo /pub/Software/pd/ (here goes the path under which you access your home dir on the web server)
After that each time you want to publish your changes just use the command from your working repository: git push --all --tags pubrepo
I think this would be much the same for each public git-hosting such as github or gitorious. You just will need to set up the transport (ssh, etc) to access it and change the single 'git remote add ...' accordingly.
Miller Puckette wrote:
Ok... I put it up on http://crca.ucsd.edu/~msp/Software/pd-git/ - I can't imagine this would work too well since the git repository mostly consists of a single compressed 4M file, which presumably your git client has to download wholesale. But if it functions for you (or if you can suggest a way I could do it better) that's easy for me to maintain :)
i was delighted when i found out about the "git-svn" bridge, which allows you to checkout an svn-repo via git, work with git and then push the changes from the local git repository to subversion.
this might be simliar to what you do know, with the noteable difference, that the history of changes will be preserved (once you push to svn, git-svn will actually do multiple commits to the svn-repository), so we have the full log of the git repository in svn.
i currently do not see a big need to setup a git-repository on sourceforge (people are still staggering about the cvs vs svn...), though i think it should be not more work than just clicking on "yes i do want to have git".
fgmadsr IOhannes
Since you are also thinking about packaging, it would be good to open
up a discussion about how to handle some things. If you plan on just
packaging pd-vanilla, then its easy. If you want to support multiple
versions of Pd then it gets a bit more complicated.
Basically, libraries/externals can't be installed into 'pd/extra'
because then the packages would conflict. I proposed /usr/lib/pd-
externals/ as a place to install all packaged externals, so then you
could have pd-vanilla, pd-extended, desiredata, etc. installed and
they could all use the externals. Claude of pure-dyne had an
objection to this, but he didn't follow up on the details.
In any case, I think we should discuss it here so we can work out a
common solution.
.hc
On May 16, 2009, at 10:31 AM, Timur Batyrshin wrote:
Hi all!
I am going to build and maintain RPM of puredata for ALT Linux. It uses git for building RPM packages so I want to pull from existing RCS (git preferrably) repositories of pd-vanilla and pd-extended if
any.So my question is:
Is there a working git repository of pd-vanilla and/or pd-extended or is the development held in SVN or such? Found only tarball of git repository on Miller Puckette's page (which obviously not exactly what I need) but no other links to git repositories.
Thanks for any advice in advance.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away to benefit those who profit from
scarcity." -John Gilmore
В Sat, 16 May 2009 19:40:31 -0400 Hans-Christoph Steiner hans@at.or.at пишет:
Basically, libraries/externals can't be installed into 'pd/extra'
because then the packages would conflict. I proposed /usr/lib/pd- externals/ as a place to install all packaged externals, so then you
could have pd-vanilla, pd-extended, desiredata, etc. installed and
they could all use the externals. Claude of pure-dyne had an
objection to this, but he didn't follow up on the details.
Is there a problem with standalone externals or what? If the prepackaged externals should only be linked with the "parent" Pd version then you could use %_libdir/%name/extra for such and %_libdir/pd-externals/ for the standalone
In any case, I think we should discuss it here so we can work out a
common solution.
Actually, here, at ALT Linux we have rather strict packaging requirements (no arch-specific data in /usr/share, etc) -- the package will simply not build if you don't hold to them, so my build might be different in some things from the community one.
Anyway I am still interested in discussing the packaging things in right way.
On May 17, 2009, at 12:36 PM, Timur Batyrshin wrote:
В Sat, 16 May 2009 19:40:31 -0400 Hans-Christoph Steiner hans@at.or.at пишет:
Basically, libraries/externals can't be installed into 'pd/extra' because then the packages would conflict. I proposed /usr/lib/pd- externals/ as a place to install all packaged externals, so then you could have pd-vanilla, pd-extended, desiredata, etc. installed and they could all use the externals. Claude of pure-dyne had an objection to this, but he didn't follow up on the details.
Is there a problem with standalone externals or what? If the prepackaged externals should only be linked with the "parent" Pd version then you could use %_libdir/%name/extra for such and %_libdir/pd-externals/ for the standalone
See my previous email in this thread.
In any case, I think we should discuss it here so we can work out a common solution.
Actually, here, at ALT Linux we have rather strict packaging requirements (no arch-specific data in /usr/share, etc) -- the package will simply not build if you don't hold to them, so my build might be different in some things from the community one.
Anyway I am still interested in discussing the packaging things in
right way.
As a long time Debian user, I am a huge fan of packaging things
right. I am guessing that a lot of these policies will be very
similar, so it'd be good to share the effort. For example, I just
created a pd-extended.xml and pd-extended.desktop Free Desktop files
to handle the mime type, file association, menus, etc. Those are
certainly usable in most distros.
.hc
Access to computers should be unlimited and total. - the hacker ethic
-
Chris McCormick -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
Miller Puckette -
Timur Batyrshin