Tim, All,
Before heading out with the kids for spring break, I was trying to upload the pkgbuilds to the svn server, but found I needed a bit of help. I've got the svn docs and think I got the commands right, but I'm not sure of the svn repository URL for uploading. Generally the checkout/commit url is different than the websvn url i.e. svn://svn.trinitydesktop.org/ compared to http://svn.trinitydesktop.org/. Also the space in "Trinity Packaging" will I guess take a %20 or something similar.
I have all of the PKGBUILDs updated with the OpenSource statement from etherpad. I have also created a structure of Arch/master/src to hold the pkgbuilds. They are all available here:
http://www.3111skyline.com/dl/dt/trinity/arch/master/src/
What I need to know is how I can get them to the svn.trinitydesktop.org server? Do I do a svn checkout, then modify and then a commit? Or do I just do a svn add?
Then what URL?
http://svn.trinitydesktop.org/websvn/listing.php?repname=Trinity+Packaging&a...
I know that's not right :) What say the svn experts?
Tim, All,
Before heading out with the kids for spring break, I was trying to upload the pkgbuilds to the svn server, but found I needed a bit of help. I've got the svn docs and think I got the commands right, but I'm not sure of the svn repository URL for uploading. Generally the checkout/commit url is different than the websvn url i.e. svn://svn.trinitydesktop.org/ compared to http://svn.trinitydesktop.org/. Also the space in "Trinity Packaging" will I guess take a %20 or something similar.
I have all of the PKGBUILDs updated with the OpenSource statement from etherpad. I have also created a structure of Arch/master/src to hold the pkgbuilds. They are all available here:
http://www.3111skyline.com/dl/dt/trinity/arch/master/src/
What I need to know is how I can get them to the svn.trinitydesktop.org server? Do I do a svn checkout, then modify and then a commit? Or do I just do a svn add?
Then what URL?
http://svn.trinitydesktop.org/websvn/listing.php?repname=Trinity+Packaging&a...
I know that's not right :) What say the svn experts?
You do a checkout, then copy your files to the correct directory, then commit.
From within a new directory:
svn co http://svn.trinitydesktop.org/svn/trinity-packaging/arch . --username=<your username>
Copy your files into that directory, then:
svn commit
Hope this helps!
Tim
Right before you commit, do "svn add *". This will add the stuff to your local copy of svn. After, you no longer need to use the add function except if you add something else, for which you would replace the star with the new item. To remove some, it is "svn delete item", replacing item with what you want to delete.
On 03/17/2011 01:14 PM, Kristopher Gamrat wrote:
Right before you commit, do "svn add *". This will add the stuff to your local copy of svn. After, you no longer need to use the add function except if you add something else, for which you would replace the star with the new item. To remove some, it is "svn delete item", replacing item with what you want to delete.
Thanks Tim, Kristopher, I'll give it a go after work today :)
On 03/21/2011 01:42 PM, David C. Rankin wrote:
On 03/17/2011 01:14 PM, Kristopher Gamrat wrote:
Right before you commit, do "svn add *". This will add the stuff to your local copy of svn. After, you no longer need to use the add function except if you add something else, for which you would replace the star with the new item. To remove some, it is "svn delete item", replacing item with what you want to delete.
Thanks Tim, Kristopher, I'll give it a go after work today :)
Hah!! It worked :) Arch pkgbuilds are in the svn repo. Sorry for the delay -- real world called ;-)
On Thu, Mar 24, 2011 at 11:04, David C. Rankin drankinatty@suddenlinkmail.com wrote:
On 03/21/2011 01:42 PM, David C. Rankin wrote:
On 03/17/2011 01:14 PM, Kristopher Gamrat wrote:
Right before you commit, do "svn add *". This will add the stuff to your local copy of svn. After, you no longer need to use the add function except if you add something else, for which you would replace the star with the new item. To remove some, it is "svn delete item", replacing item with what you want to delete.
Thanks Tim, Kristopher, I'll give it a go after work today :)
Hah!! It worked :) Arch pkgbuilds are in the svn repo. Sorry for the delay -- real world called ;-)
-- David C. Rankin, J.D.,P.E.
Can you please upload all these files to SVN in a non-tar.gz format? like a folder for each package. ex:
master/ trinity-kdebase/ trinity-kdelibs/ ...
On 03/24/2011 10:17 AM, Robert Xu wrote:
On Thu, Mar 24, 2011 at 11:04, David C. Rankin drankinatty@suddenlinkmail.com wrote:
On 03/21/2011 01:42 PM, David C. Rankin wrote:
On 03/17/2011 01:14 PM, Kristopher Gamrat wrote:
Right before you commit, do "svn add *". This will add the stuff to your local copy of svn. After, you no longer need to use the add function except if you add something else, for which you would replace the star with the new item. To remove some, it is "svn delete item", replacing item with what you want to delete.
Thanks Tim, Kristopher, I'll give it a go after work today :)
Hah!! It worked :) Arch pkgbuilds are in the svn repo. Sorry for the delay -- real world called ;-)
-- David C. Rankin, J.D.,P.E.
Can you please upload all these files to SVN in a non-tar.gz format? like a folder for each package. ex:
master/ trinity-kdebase/ trinity-kdelibs/ ...
Yes, but traditionally, Arch PKGBUILDS are always contained within .tar.gz packages that also contain all *needed* patches for the build. It would be somewhat meaningless to have the PKGBUILDS that require patches uploaded as plain text. (they wouldn't build anything - Qt3, etc..) At least for Trinity there are only a couple that have patches, so that will help. What I can do it create a structure like
master \PKGBUILDS \trinity-kdebase \PKGBUILD \ etc...
That would just hold the PKGBUILD files by themselves, but I suspect you want the PKGBUILD + patches in each of the directories.
I expanded and did the commit. Let me know if that is what you wanted :)
On Thu, Mar 24, 2011 at 11:59, David C. Rankin drankinatty@suddenlinkmail.com wrote:
On 03/24/2011 10:17 AM, Robert Xu wrote:
On Thu, Mar 24, 2011 at 11:04, David C. Rankin drankinatty@suddenlinkmail.com wrote:
On 03/21/2011 01:42 PM, David C. Rankin wrote:
On 03/17/2011 01:14 PM, Kristopher Gamrat wrote:
Right before you commit, do "svn add *". This will add the stuff to your local copy of svn. After, you no longer need to use the add function except if you add something else, for which you would replace the star with the new item. To remove some, it is "svn delete item", replacing item with what you want to delete.
Thanks Tim, Kristopher, I'll give it a go after work today :)
Hah!! It worked :) Arch pkgbuilds are in the svn repo. Sorry for the delay -- real world called ;-)
-- David C. Rankin, J.D.,P.E.
Can you please upload all these files to SVN in a non-tar.gz format? like a folder for each package. ex:
master/ trinity-kdebase/ trinity-kdelibs/ ...
Yes, but traditionally, Arch PKGBUILDS are always contained within .tar.gz packages that also contain all *needed* patches for the build. It would be somewhat meaningless to have the PKGBUILDS that require patches uploaded as plain text. (they wouldn't build anything - Qt3, etc..) At least for Trinity there are only a couple that have patches, so that will help. What I can do it create a structure like
master \PKGBUILDS \trinity-kdebase \PKGBUILD \ etc...
That would just hold the PKGBUILD files by themselves, but I suspect you want the PKGBUILD + patches in each of the directories.
I expanded and did the commit. Let me know if that is what you wanted :)
Yup! Please remove the svn-commit.tmp though :P
On 03/24/2011 12:36 PM, Robert Xu wrote:
I expanded and did the commit. Let me know if that is what you wanted :)
Yup! Please remove the svn-commit.tmp though :P
When I do a svn commit, I always get a temp screen that says eg.:
--This line, and those below, will be ignored--
D svn-commit.tmp
It's open in the default editor vi, so I just delete the line and :wq and it works. Is there a way to not get this line?
On Thu, Mar 24, 2011 at 18:08, David C. Rankin drankinatty@suddenlinkmail.com wrote:
On 03/24/2011 12:36 PM, Robert Xu wrote:
I expanded and did the commit. Let me know if that is what you wanted :)
Yup! Please remove the svn-commit.tmp though :P
When I do a svn commit, I always get a temp screen that says eg.:
--This line, and those below, will be ignored--
D svn-commit.tmp
It's open in the default editor vi, so I just delete the line and :wq and it works. Is there a way to not get this line?
No, don't edit that line. You WANT svn-commit.tmp to be deleted. You should not edit anything below the line.
On 03/24/2011 06:30 PM, Robert Xu wrote:
When I do a svn commit, I always get a temp screen that says eg.:
--This line, and those below, will be ignored--
D svn-commit.tmp
It's open in the default editor vi, so I just delete the line and :wq and it works. Is there a way to not get this line?
No, don't edit that line. You WANT svn-commit.tmp to be deleted. You should not edit anything below the line.
Hmmm.... I deleted it. That was the only way to delete the svn-commit.tmp file. Otherwise the:
D svn-commit.tmp
line would have been ignored (If I read it correctly....) So I guess I just need to back up and ask:
--This line, and those below, will be ignored--
What the heck is this line above??
On Thu, Mar 24, 2011 at 23:02, David C. Rankin drankinatty@suddenlinkmail.com wrote:
Hmmm.... I deleted it. That was the only way to delete the svn-commit.tmp file. Otherwise the:
D svn-commit.tmp
line would have been ignored (If I read it correctly....) So I guess I just need to back up and ask:
No.
--This line, and those below, will be ignored--
What the heck is this line above??
You put the summary of your changes (the commit message) above that line. Below that line is the complete file list and changes.
-
David C. Rankin -
Kristopher Gamrat -
Robert Xu -
Timothy Pearson