Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 21 Dec 2014, 17:10
All times are UTC - 4
 Forum index » Taking the Puppy out for a walk » Announcements
Google Code Page for Puppy Development
Moderators: Flash, Ian, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 3 of 3 Posts_count   Goto page: Previous 1, 2, 3
Author Message
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Tue 13 Oct 2009, 13:06    Post_subject:  

From http://www.murga-linux.com/puppy/viewtopic.php?p=350864#350864:
Lobster wrote:
Reporting bugs - easy
checking out code - did not seem easy
- in fact I could add a comment to code but not check out
this was with Jeremys code (Pizzasgood)
- eh did you lock it so crazy cructaceans can not check it out
or am I just incompetent? (probably incompetent) Embarassed

If I wanted to checkout the trunk of the Edit-SFS program, I would do this:
Code:
svn checkout http://puppy-development.googlecode.com/svn/trunk/edit-sfs/trunk edit-sfs_trunk

That would create the directory edit-sfs_trunk on my local filesystem, containing everything in the /trunk/edit-sfs/trunk/ directory of the repository. If I wanted the entire Edit-SFS project, I would do this:
Code:
svn checkout http://puppy-development.googlecode.com/svn/trunk/edit-sfs edit-sfs

That would create the directory edit-sfs on my local filesystem, containing everything from /trunk/edit-sfs/.

Both of those examples are for people who don't intend to commit changes back to SVN, i.e. users or package makers who just want to grab the latest version. Developers who intend to commit changes can use very similar commands, except that instead of http:// they would use https://, and they would also need to add the --username youremail@gmail.com option. So, if I were a developer with an address of amadeus@gmail.com, I would do this:
Code:
svn checkout https://puppy-development.googlecode.com/svn/trunk/edit-sfs edit-sfs --username amadeus@gmail.com

That would then prompt me for my googlecode password, which google generates randomly for you and is obtainable from your googlecode profile, I believe. You should only need to do that once. From there out, unless you've configured SVN otherwise, it will remember your name and password when working with that working tree, and possibly the entire Puppy SVN repo (not sure about that part, I haven't used SVN much since spring).


People should observe some form of etiquette when committing to somebody else's project, such as making their own branch (in /trunk/<project-name>/branches/) so they don't step on anybody's toes, unless they've talked to those in charge of that particular project and gotten permission to commit to the trunk or official branches. Different people and projects might have different workflows, so contributors should also be aware of that. For example, on Edit-SFS I'm just doing all the work in the trunk, and occasionally I might tag a release version. For more complex projects, I might prefer to use a development branch and consider the trunk the stable branch, so that at any time somebody could checkout the latest snapshot of the trunk and have a working, if unfinished, version of the code.

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send_private_message Visit_website 
technosaurus


Joined: 18 May 2008
Posts: 4424

PostPosted: Tue 13 Oct 2009, 13:31    Post_subject:  

I've been thinking of how to organize this also, not just for source code but also for package maintenance.

---[Extras (pinstall.sh, .desktop, pixmaps, additional scripts.... in a proper tree so it can be directly copied)

---[src (for puppy projects or non compiled programs) Outside projects would have a file with a link to the main project

...Notes_Changelog (best configure options, files to add/modify/delete after compile, other nuances,...)

...config file (contains the compile options used to best compile the program)

...Latest_stable_pet(s)??<-- How fast would we use up 1GB - Google would likely increase the limit but....still maybe just a link

What else is missing? I would like to build a tree with the basic stubs already there.

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send_private_message 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Tue 13 Oct 2009, 13:50    Post_subject:  

Something to be wary of: SVN likes to place a hidden .svn/ directory inside of every directory in the repository. So if you set up a tree expecting to literally copy/paste it into a build environment or compress it into a package, you need to either use something like 'svn dump' (I think, haven't looked at it in a while), or else run a script on a copy of the data to remove all .svn/ directories (don't do that to the originals in the SVN working dir or you'll break it).

That's one of the reasons I organized the Edit-SFS project as I did (no directories, and a Makefile to put everything together) even though it doesn't actually have anything to compile. When I want a directory tree I can just run make dir and it appears, nice and clean. I can use make pet to make a .pet. I can use make clean to clear all that out and restore me to a clean SVN checkout.


Also, IIRC SVN doesn't work with device nodes, and probably not with permissions, so if you make a package that contains dev nodes or files that need special permissions, you'll have to have the pinstall.sh script create/set them or something.

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send_private_message Visit_website 
technosaurus


Joined: 18 May 2008
Posts: 4424

PostPosted: Tue 13 Oct 2009, 14:27    Post_subject:  

Good pointer/hack PG. Can't you also use tar to exclude .svn somehow when making a tarball? I don't recall the option. I will definitely have to test the permissions though - That would not be good. (If so, your Makefile option should get around permissions also, assuming appropriate chmod is set up in the Makefile, correct?)
_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send_private_message 
Pizzasgood


Joined: 04 May 2005
Posts: 6270
Location: Knoxville, TN, USA

PostPosted: Tue 13 Oct 2009, 15:09    Post_subject:  

tar --exclude-vcs will do the trick. I didn't know about that. Cool.

You can also use rsync instead of cp when copying things to filter out directories matching a pattern, but you have to be a lot more careful about how you write the target and destination names with rsync (it attaches significance to the presence of a trailing / to determine how you want to copy things (renaming, copy into, copy over, etc.)).

I just did some quick testing, and apparently SVN will track the execute bit when a file is added but not after the file exists. The other bits were all ignored.

_________________
Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Back to top
View user's profile Send_private_message Visit_website 
Aitch


Joined: 04 Apr 2007
Posts: 6825
Location: Chatham, Kent, UK

PostPosted: Tue 13 Oct 2009, 21:14    Post_subject:  

here's a link needs some comment, please

Quote:
Many years ago, IBM inspector asked me for our QC manual to approve us as a vendor. We had a copy from Transitron that we have adopted.

Today, Puppy is trying to standardize their filename creation without a QC manual as a reference.

So, its time for Ted T'so to get a copy of QC manual from IBM to run Linux coding. Its never too late, but Linux is a business, you have to run it as a professional.

All these newbies writing codes have no idea even, on how to submit codes to a maintainer? A QC manual will help to have traceability and inspector signature to assure quality of software?


http://www.tuxmachines.org/node/35889

Aitch Smile
Back to top
View user's profile Send_private_message 
mikeb


Joined: 23 Nov 2006
Posts: 9060

PostPosted: Sun 29 Nov 2009, 10:08    Post_subject:  

Erm no issues on the bugtracker and I had another I had found.....what's happening

mike
Back to top
View user's profile Send_private_message 
technosaurus


Joined: 18 May 2008
Posts: 4424

PostPosted: Mon 30 Nov 2009, 17:33    Post_subject:  

The direct link still works... The wiki page for "issues" overrides the issue tracker list. This is a good place for a "how to file a good bug report" message. I made a quick temporary edit that points to the actuall issue list
_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send_private_message 
mikeb


Joined: 23 Nov 2006
Posts: 9060

PostPosted: Mon 30 Nov 2009, 17:48    Post_subject:  

Quote:
I made a quick temporary edit that points to the actuall issue list


thanks Smile

mike
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 3 of 3 Posts_count   Goto page: Previous 1, 2, 3
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Taking the Puppy out for a walk » Announcements
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0727s ][ Queries: 13 (0.0052s) ][ GZIP on ]