Garvin is kinly helping me with a bug I reported. He mentioned he had commited a change he posted.. so I got curious..
Where/how can one download the latest code?
Looked through the site, and even found a CVS tree viewer online, but did not see any info on how to get latest code.
Did I miss this info on the site?
Part of my confusion is that I recall reading some info on Subversion usage for this project, yet it seems there is a CVS repository at SF.net
Where/How to get current source tree
Searching through the foruns found this address
svn://svn.berlios.de/serendipity/trunk
Is that the latest code?
How about the "stable".. latest production?
Also how about the additional plugins?
Did a search on the downloaded files and did not see the static pluging which is what I was looking for.
[Edit]
What is the difference between the Berlios repository and the Sourceforge repository?
svn://svn.berlios.de/serendipity/trunk
Is that the latest code?
How about the "stable".. latest production?
Also how about the additional plugins?
Did a search on the downloaded files and did not see the static pluging which is what I was looking for.
[Edit]
What is the difference between the Berlios repository and the Sourceforge repository?
The latest SVN commits are available under 'trunk' subfolder of the BerliOS
SVN repository for s9y. This is essentially what the nightly snapshots are
created with... the current ongoing 'alpha' version of 0.9.
The stable production files are found in the SourceForge CVS repository for
s9y, as well as under 'tags' subfolder of the BerliOS SVN.
All the additional plug-ins and themes are found at SF CVS under the easily
distinguishable names.
It used to be that every s9y developments were happening on SF CVS, but
now the main code itself is being developed in BOS SVN, while the rest of
the stuff are still updated at SF CVS.
Static Pages plug-in is not a part of the main code, so you need to get the
latest version from SF CVS.
SVN repository for s9y. This is essentially what the nightly snapshots are
created with... the current ongoing 'alpha' version of 0.9.
The stable production files are found in the SourceForge CVS repository for
s9y, as well as under 'tags' subfolder of the BerliOS SVN.
All the additional plug-ins and themes are found at SF CVS under the easily
distinguishable names.
It used to be that every s9y developments were happening on SF CVS, but
now the main code itself is being developed in BOS SVN, while the rest of
the stuff are still updated at SF CVS.
Static Pages plug-in is not a part of the main code, so you need to get the
latest version from SF CVS.
I make s9y plugins, too.
My s9y blog depends on them.
My s9y blog depends on them.
How can I download from sourceforge the additional plugins?
Tried
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/php-blog login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/php-blog co
but got prompted for a password.
Also tried with my sourceforge ID but get error
cvs [checkout aborted]: must specify at least one module or directory
Tried to pass the name additional_plugins and got Permission denied.
Tried
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/php-blog login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/php-blog co
but got prompted for a password.
Also tried with my sourceforge ID but get error
cvs [checkout aborted]: must specify at least one module or directory
Tried to pass the name additional_plugins and got Permission denied.
Well, I didn't initiate the move, so I'll leave that question to someone else.
Meanwhile, I don't use command-line CVS tool, but just SmartCVS, and
using :pserver:anonymous@cvs.sourceforge.net:/cvsroot/php-blog for
the parameters worked fine for me.
Shouldn't
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/php-blog co -P additional_plugins
work, though?
Meanwhile, I don't use command-line CVS tool, but just SmartCVS, and
using :pserver:anonymous@cvs.sourceforge.net:/cvsroot/php-blog for
the parameters worked fine for me.
Shouldn't
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/php-blog co -P additional_plugins
work, though?
I make s9y plugins, too.
My s9y blog depends on them.
My s9y blog depends on them.
-
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Just a drop-in: We are using SF.Net for plugins because more people have SF.Net accounts for contributing code, and more people are familiar with CVS instead of SVN.
Since we still need contributions, we try to make it as easy for the user as possible. Actually only "real" developers of the Serendipity core would need to fiddle with SVN.
(The nightlies are also done from the SVN trunk)
Regards,
Garvin
Since we still need contributions, we try to make it as easy for the user as possible. Actually only "real" developers of the Serendipity core would need to fiddle with SVN.
(The nightlies are also done from the SVN trunk)
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Ok.garvinhicking wrote:Just a drop-in: We are using SF.Net for plugins because more people have SF.Net accounts for contributing code, and more people are familiar with CVS instead of SVN.
In my experience, as a newbie in the project, I think it actually makes it more difficult for new users trying to help that the code is in two separate sites under 2 different version control systems.. They will have to go to 2 places if they want to get involved with all aspects of the code AND get two programs (or learn two sytax) to get data in bulk from the tree.garvinhicking wrote:Since we still need contributions, we try to make it as easy for the user as possible. Actually only "real" developers of the Serendipity core would need to fiddle with SVN.
(The nightlies are also done from the SVN trunk)
For now I am using the webcvs at SF to get the selected files I need.
Well, it's like 'level of access' stuff, I guess. Unless the plugin developments
require the latest development code, the ones uploaded at SF should suffice.
require the latest development code, the ones uploaded at SF should suffice.
I make s9y plugins, too.
My s9y blog depends on them.
My s9y blog depends on them.