Re: [leaf-devel] next steps
On Wed, 2011-02-09 at 23:50 +0200, Andrew wrote: 09.02.2011 00:05, KP Kirchdoerfer пишет: Am Sonntag, 6. Februar 2011, um 12:14:16 schrieb ads...@genis-x.com: Is anyone able to push all the contrib packages into git? All package sources has been moved into git. kp: Thank you. I know how much work that must have been. You are a hero! Pls test and give feedback if it works - or report back errors you detect while building the packages. thx kp All looks OK. I moved all sources into buildtool/repo dir, and added new server type - 'filesymlnk' that works like 'file' server type, but just creates symlinks instead of file copying - to avoid space wasting. Now all sources are placed into single place and it is no needed to re-download all of them from overloaded SF servers. Of course, this is a dirty hack; in future it'll be good to rewrite buildtool logic to work with source tree w/o copying of files (or even choose other building environment) - but it'll be later. P.S. I think that we should move all from bering-uclibc4 dir into root of git? I think that in any case we shouldn't have 2 or more branches paralelly into one repository - it's easy to create new repo for major modifications, and it's easy to maintain separate repo branches for minor changes. IMHO we should retain a bering-uclibc4 level somewhere. Git is for the whole of LEAF, not just for bering-uclib4, and one day there will be a bering-uclibc5... Right now we have a repo called leaf within a project called leaf. How about naming the repo to bering-uclibc4 and then removing being-uclibc4 as a directory level within the repo? dMb -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
12.02.2011 12:39, davidMbrooke пишет: On Wed, 2011-02-09 at 23:50 +0200, Andrew wrote: 09.02.2011 00:05, KP Kirchdoerfer пишет: Am Sonntag, 6. Februar 2011, um 12:14:16 schrieb ads...@genis-x.com: Is anyone able to push all the contrib packages into git? All package sources has been moved into git. kp: Thank you. I know how much work that must have been. You are a hero! Pls test and give feedback if it works - or report back errors you detect while building the packages. thx kp All looks OK. I moved all sources into buildtool/repo dir, and added new server type - 'filesymlnk' that works like 'file' server type, but just creates symlinks instead of file copying - to avoid space wasting. Now all sources are placed into single place and it is no needed to re-download all of them from overloaded SF servers. Of course, this is a dirty hack; in future it'll be good to rewrite buildtool logic to work with source tree w/o copying of files (or even choose other building environment) - but it'll be later. P.S. I think that we should move all from bering-uclibc4 dir into root of git? I think that in any case we shouldn't have 2 or more branches paralelly into one repository - it's easy to create new repo for major modifications, and it's easy to maintain separate repo branches for minor changes. IMHO we should retain a bering-uclibc4 level somewhere. Git is for the whole of LEAF, not just for bering-uclib4, and one day there will be a bering-uclibc5... Right now we have a repo called leaf within a project called leaf. How about naming the repo to bering-uclibc4 and then removing being-uclibc4 as a directory level within the repo? dMb This will be OK. I didn't create other repo when I pushed LEAF into it because SSH acces was down; now it should work. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
09.02.2011 00:05, KP Kirchdoerfer пишет: Am Sonntag, 6. Februar 2011, um 12:14:16 schrieb ads...@genis-x.com: Is anyone able to push all the contrib packages into git? All package sources has been moved into git. Pls test and give feedback if it works - or report back errors you detect while building the packages. thx kp All looks OK. I moved all sources into buildtool/repo dir, and added new server type - 'filesymlnk' that works like 'file' server type, but just creates symlinks instead of file copying - to avoid space wasting. Now all sources are placed into single place and it is no needed to re-download all of them from overloaded SF servers. Of course, this is a dirty hack; in future it'll be good to rewrite buildtool logic to work with source tree w/o copying of files (or even choose other building environment) - but it'll be later. P.S. I think that we should move all from bering-uclibc4 dir into root of git? I think that in any case we shouldn't have 2 or more branches paralelly into one repository - it's easy to create new repo for major modifications, and it's easy to maintain separate repo branches for minor changes. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
Am Sonntag, 6. Februar 2011, um 12:14:16 schrieb ads...@genis-x.com: Is anyone able to push all the contrib packages into git? All package sources has been moved into git. Pls test and give feedback if it works - or report back errors you detect while building the packages. thx kp -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
Is anyone able to push all the contrib packages into git? -Original Message- From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] Sent: Saturday, 5 February 2011 11:32 PM To: leaf-devel Subject: Re: [leaf-devel] next steps On Thu, 2011-02-03 at 07:07 -0800, Mike Noyes wrote: On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: This is quite easy: do git clone and set personal data (name/email); copy bering-uclibc/apps and bering-uclibc/contrib into git dir; modify config files (replace server names) into sources' buildenv.conf; do git add * and then do git commit and git push. After short look in leaf-commits mailing list, in current git snapshot only last busybox commit (update to 1.18.2) is missed. Andrew, Is git functional for continued development, or are further actions necessary? Everyone, Here are a few links to help everyone get up to speed on git: http://sourceforge.net/apps/trac/sourceforge/wiki/Git http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://git-scm.com/documentation GitWeb http://leaf.git.sourceforge.net/ Thanks Mike. I have created a new wiki page for hints and tips on using Git for LEAF as Appendix 2 in the Developer Guide, direct link is: http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x _-_Developer_Guide_-_Hints_and_Tips_for_using_Git_SCM Personally I am new to Git and I plan to spend several hours investigating it over the weekend. I have already spotted some things that I think could be improved (see the Discussion page on the wiki) so I suggest the main developers review the status in a couple of days. I have no doubt that Git is the right new SCM tool for LEAF but it has some different concepts from CVS and we may need to refine our approach. dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Sun, 2011-02-06 at 22:14 +1100, ads...@genis-x.com wrote: Is anyone able to push all the contrib packages into git? Hi Ad, Your messages aren't showing up in leaf-devel for some reason, even though you seem to specify the right address in the Cc: field. There are people with the capability to push to git, but maybe they don't have the time or the motivation right now :-) I see that kp has made a start (haserl and pwcrypt). Do you have a definitive list of what is missing? I can do a few Packages but I don't have time to do 20. I am still learning Git (and writing the Wiki page as I go) which slows things down. I suspect that Git is also wide open for write access right now, so others could help with this job if we can co-ordinate the team. dMb -Original Message- From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] Sent: Saturday, 5 February 2011 11:32 PM To: leaf-devel Subject: Re: [leaf-devel] next steps On Thu, 2011-02-03 at 07:07 -0800, Mike Noyes wrote: On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: This is quite easy: do git clone and set personal data (name/email); copy bering-uclibc/apps and bering-uclibc/contrib into git dir; modify config files (replace server names) into sources' buildenv.conf; do git add * and then do git commit and git push. After short look in leaf-commits mailing list, in current git snapshot only last busybox commit (update to 1.18.2) is missed. Andrew, Is git functional for continued development, or are further actions necessary? Everyone, Here are a few links to help everyone get up to speed on git: http://sourceforge.net/apps/trac/sourceforge/wiki/Git http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://git-scm.com/documentation GitWeb http://leaf.git.sourceforge.net/ Thanks Mike. I have created a new wiki page for hints and tips on using Git for LEAF as Appendix 2 in the Developer Guide, direct link is: http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x _-_Developer_Guide_-_Hints_and_Tips_for_using_Git_SCM Personally I am new to Git and I plan to spend several hours investigating it over the weekend. I have already spotted some things that I think could be improved (see the Discussion page on the wiki) so I suggest the main developers review the status in a couple of days. I have no doubt that Git is the right new SCM tool for LEAF but it has some different concepts from CVS and we may need to refine our approach. dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Sun, 2011-02-06 at 12:17 +, davidMbrooke wrote: On Sun, 2011-02-06 at 22:14 +1100, ads...@genis-x.com wrote: Is anyone able to push all the contrib packages into git? Hi Ad, Your messages aren't showing up in leaf-devel for some reason, even though you seem to specify the right address in the Cc: field. There are people with the capability to push to git, but maybe they don't have the time or the motivation right now :-) I see that kp has made a start (haserl and pwcrypt). Do you have a definitive list of what is missing? I can do a few Packages but I don't have time to do 20. I am still learning Git (and writing the Wiki page as I go) which slows things down. I suspect that Git is also wide open for write access right now, so others could help with this job if we can co-ordinate the team. dMb I have added a few of the missing source Packages: - keyboard - hdparm (which was WAY out of date so I upgraded to the latest) - this also fixes the failure on hdsupp - upnpbridge - pcre (also old so I upgraded) - this also fixes the failure on kismet Plenty more to fix though! dMb -Original Message- From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] Sent: Saturday, 5 February 2011 11:32 PM To: leaf-devel Subject: Re: [leaf-devel] next steps On Thu, 2011-02-03 at 07:07 -0800, Mike Noyes wrote: On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: This is quite easy: do git clone and set personal data (name/email); copy bering-uclibc/apps and bering-uclibc/contrib into git dir; modify config files (replace server names) into sources' buildenv.conf; do git add * and then do git commit and git push. After short look in leaf-commits mailing list, in current git snapshot only last busybox commit (update to 1.18.2) is missed. Andrew, Is git functional for continued development, or are further actions necessary? Everyone, Here are a few links to help everyone get up to speed on git: http://sourceforge.net/apps/trac/sourceforge/wiki/Git http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://git-scm.com/documentation GitWeb http://leaf.git.sourceforge.net/ Thanks Mike. I have created a new wiki page for hints and tips on using Git for LEAF as Appendix 2 in the Developer Guide, direct link is: http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x _-_Developer_Guide_-_Hints_and_Tips_for_using_Git_SCM Personally I am new to Git and I plan to spend several hours investigating it over the weekend. I have already spotted some things that I think could be improved (see the Discussion page on the wiki) so I suggest the main developers review the status in a couple of days. I have no doubt that Git is the right new SCM tool for LEAF but it has some different concepts from CVS and we may need to refine our approach. dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Thu, 2011-02-03 at 07:07 -0800, Mike Noyes wrote: On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: This is quite easy: do git clone and set personal data (name/email); copy bering-uclibc/apps and bering-uclibc/contrib into git dir; modify config files (replace server names) into sources' buildenv.conf; do git add * and then do git commit and git push. After short look in leaf-commits mailing list, in current git snapshot only last busybox commit (update to 1.18.2) is missed. Andrew, Is git functional for continued development, or are further actions necessary? Everyone, Here are a few links to help everyone get up to speed on git: http://sourceforge.net/apps/trac/sourceforge/wiki/Git http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://git-scm.com/documentation GitWeb http://leaf.git.sourceforge.net/ Thanks Mike. I have created a new wiki page for hints and tips on using Git for LEAF as Appendix 2 in the Developer Guide, direct link is: http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x_-_Developer_Guide_-_Hints_and_Tips_for_using_Git_SCM Personally I am new to Git and I plan to spend several hours investigating it over the weekend. I have already spotted some things that I think could be improved (see the Discussion page on the wiki) so I suggest the main developers review the status in a couple of days. I have no doubt that Git is the right new SCM tool for LEAF but it has some different concepts from CVS and we may need to refine our approach. dMb -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: This is quite easy: do git clone and set personal data (name/email); copy bering-uclibc/apps and bering-uclibc/contrib into git dir; modify config files (replace server names) into sources' buildenv.conf; do git add * and then do git commit and git push. After short look in leaf-commits mailing list, in current git snapshot only last busybox commit (update to 1.18.2) is missed. Andrew, Is git functional for continued development, or are further actions necessary? Everyone, Here are a few links to help everyone get up to speed on git: http://sourceforge.net/apps/trac/sourceforge/wiki/Git http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://git-scm.com/documentation GitWeb http://leaf.git.sourceforge.net/ -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
03.02.2011 17:07, Mike Noyes пишет: On Tue, 2011-02-01 at 23:08 +0200, Andrew wrote: This is quite easy: do git clone and set personal data (name/email); copy bering-uclibc/apps and bering-uclibc/contrib into git dir; modify config files (replace server names) into sources' buildenv.conf; do git add * and then do git commit and git push. After short look in leaf-commits mailing list, in current git snapshot only last busybox commit (update to 1.18.2) is missed. Andrew, Is git functional for continued development, or are further actions necessary? It's needed to upload all required sources from old bering-uClibc into git, and it'll be good to add .gitignore with paths for temporary/work files (/source dir, /packages and so on) - to make easily compiling from buildenv from git without pushing generated binary files into it. Of course, in future it'll be good to make single GIT repository w/o need of downloading files separately - but this will be considered as improvement of usability, not as bug/1st-priority target. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
31.01.2011 23:06, Mike Noyes пишет: Charles, I just enabled svn for our project again. Git is enabled also, but I suspect migration to git is more complex. I think that migration to any SCM is trivial till it's possible to get access to source tree (latest version of files) via HTTP. And gitweb provides this at 1st look. Link to latest revision of file path/filename looks like this: http://projectname.git.sourceforge.net/git/gitweb.cgi?p=path;a=blob_plain;f=filename;hb=HEAD -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: 31.01.2011 23:06, Mike Noyes пишет: Charles, I just enabled svn for our project again. Git is enabled also, but I suspect migration to git is more complex. I think that migration to any SCM is trivial till it's possible to get access to source tree (latest version of files) via HTTP. And gitweb provides this at 1st look. Link to latest revision of file path/filename looks like this: http://projectname.git.sourceforge.net/git/gitweb.cgi?p=path;a=blob_pla in;f=filename;hb=HEAD Latest versions should be possible, Charles rsync backup seems to be valid, I have the latest packages and sources in my local cvs copy, and finally SF should have a backup as well. IMHO non-trivial are the changes needed for buildtool (a new scm downloader is needed, the sources.cfg needs rework and probably every buildtool.mk file). Also we need to change the documentation, helper files like genpage.sh and maybe some more corner stuff. That's why I'd like to have a stable version first and move to a new SCM later, IF possible... kp -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
01.02.2011 14:02, KP Kirchdoerfer пишет: Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: 31.01.2011 23:06, Mike Noyes пишет: Charles, I just enabled svn for our project again. Git is enabled also, but I suspect migration to git is more complex. I think that migration to any SCM is trivial till it's possible to get access to source tree (latest version of files) via HTTP. And gitweb provides this at 1st look. Link to latest revision of file path/filename looks like this: http://projectname.git.sourceforge.net/git/gitweb.cgi?p=path;a=blob_pla in;f=filename;hb=HEAD Latest versions should be possible, Charles rsync backup seems to be valid, I have the latest packages and sources in my local cvs copy, and finally SF should have a backup as well. IMHO non-trivial are the changes needed for buildtool (a new scm downloader is needed, the sources.cfg needs rework and probably every buildtool.mk file). Also we need to change the documentation, helper files like genpage.sh and maybe some more corner stuff. That's why I'd like to have a stable version first and move to a new SCM later, IF possible... kp Buildtool actually takes data from CVS via http. And it isn't too hard to modify ViewCVS.pm to take data from git via gitweb - like from CVS via viewvc. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Tue, 2011-02-01 at 14:15 +0200, Andrew wrote: 01.02.2011 14:02, KP Kirchdoerfer пишет: Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: 31.01.2011 23:06, Mike Noyes пишет: Charles, I just enabled svn for our project again. Git is enabled also, but I suspect migration to git is more complex. I think that migration to any SCM is trivial till it's possible to get access to source tree (latest version of files) via HTTP. And gitweb provides this at 1st look. Link to latest revision of file path/filename looks like this: http://projectname.git.sourceforge.net/git/gitweb.cgi?p=path;a=blob_pla in;f=filename;hb=HEAD Latest versions should be possible, Charles rsync backup seems to be valid, I have the latest packages and sources in my local cvs copy, and finally SF should have a backup as well. IMHO non-trivial are the changes needed for buildtool (a new scm downloader is needed, the sources.cfg needs rework and probably every buildtool.mk file). Also we need to change the documentation, helper files like genpage.sh and maybe some more corner stuff. That's why I'd like to have a stable version first and move to a new SCM later, IF possible... kp Buildtool actually takes data from CVS via http. And it isn't too hard to modify ViewCVS.pm to take data from git via gitweb - like from CVS via viewvc. Everyone, My preference is a move to git, provided buildtool SCM transition is equal. The git community is dominating SCMs (see github). However, project member training (commands, distributed nature, etc.) is steeper than a move to SVN. +1 Git I propose Charles work on SVN and Andrew work on Git, so we can see what issues arise. This should allow our developers to make a decision on which SCM will serve our community best. Andrew, Please let me know if you have access to our git repository. https://sourceforge.net/apps/trac/sourceforge/wiki/Git KP, I agree that a stable release is preferable prior to SCM migration. Do you have an estimate for completion of a stable release? -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
01.02.2011 17:37, Mike Noyes пишет: On Tue, 2011-02-01 at 14:15 +0200, Andrew wrote: 01.02.2011 14:02, KP Kirchdoerfer пишет: Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: 31.01.2011 23:06, Mike Noyes пишет: Charles, I just enabled svn for our project again. Git is enabled also, but I suspect migration to git is more complex. I think that migration to any SCM is trivial till it's possible to get access to source tree (latest version of files) via HTTP. And gitweb provides this at 1st look. Link to latest revision of file path/filename looks like this: http://projectname.git.sourceforge.net/git/gitweb.cgi?p=path;a=blob_pla in;f=filename;hb=HEAD Latest versions should be possible, Charles rsync backup seems to be valid, I have the latest packages and sources in my local cvs copy, and finally SF should have a backup as well. IMHO non-trivial are the changes needed for buildtool (a new scm downloader is needed, the sources.cfg needs rework and probably every buildtool.mk file). Also we need to change the documentation, helper files like genpage.sh and maybe some more corner stuff. That's why I'd like to have a stable version first and move to a new SCM later, IF possible... kp Buildtool actually takes data from CVS via http. And it isn't too hard to modify ViewCVS.pm to take data from git via gitweb - like from CVS via viewvc. Everyone, My preference is a move to git, provided buildtool SCM transition is equal. The git community is dominating SCMs (see github). However, project member training (commands, distributed nature, etc.) is steeper than a move to SVN. +1 Git I propose Charles work on SVN and Andrew work on Git, so we can see what issues arise. This should allow our developers to make a decision on which SCM will serve our community best. Andrew, Please let me know if you have access to our git repository. https://sourceforge.net/apps/trac/sourceforge/wiki/Git Yes, I have access. Now migration almost complete - I uploaded partial snapshot into git (snapshot of bering-uclibc4 tree), and updated buildtool logic to work with git. At least, buildtool.pl source linux works OK - so I expect no troubles. As I said, migration is trivial :) I added new paremeter for both server and source package - Repo, which contains pair project/repository (by default - leaf/leaf) - this will make multi-branch development easier. For completion I need that somebody push latest available snapshot into git with modified server names into packages (cvs-sourceforge is replaced by leaf-sourceforge, cvs4-sourceforge is replaced by leaf4-sourceforge and so on). I did this by shell command find . -name buildtool.cfg | xargs perl -i -p -e 's/cvs4-/leaf4-/g;s/cvs-/leaf-/g' into source tree, it may be inaccurate, but at 1st look it doesn't replace anything except server name. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Tue, 2011-02-01 at 22:27 +0200, Andrew wrote: 01.02.2011 17:37, Mike Noyes пишет: On Tue, 2011-02-01 at 14:15 +0200, Andrew wrote: 01.02.2011 14:02, KP Kirchdoerfer пишет: Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: 31.01.2011 23:06, Mike Noyes пишет: Charles, I just enabled svn for our project again. Git is enabled also, but I suspect migration to git is more complex. I think that migration to any SCM is trivial till it's possible to get access to source tree (latest version of files) via HTTP. And gitweb provides this at 1st look. Link to latest revision of file path/filename looks like this: http://projectname.git.sourceforge.net/git/gitweb.cgi?p=path;a=blob_pla in;f=filename;hb=HEAD Latest versions should be possible, Charles rsync backup seems to be valid, I have the latest packages and sources in my local cvs copy, and finally SF should have a backup as well. IMHO non-trivial are the changes needed for buildtool (a new scm downloader is needed, the sources.cfg needs rework and probably every buildtool.mk file). Also we need to change the documentation, helper files like genpage.sh and maybe some more corner stuff. That's why I'd like to have a stable version first and move to a new SCM later, IF possible... kp Buildtool actually takes data from CVS via http. And it isn't too hard to modify ViewCVS.pm to take data from git via gitweb - like from CVS via viewvc. Everyone, My preference is a move to git, provided buildtool SCM transition is equal. The git community is dominating SCMs (see github). However, project member training (commands, distributed nature, etc.) is steeper than a move to SVN. +1 Git I propose Charles work on SVN and Andrew work on Git, so we can see what issues arise. This should allow our developers to make a decision on which SCM will serve our community best. Andrew, Please let me know if you have access to our git repository. https://sourceforge.net/apps/trac/sourceforge/wiki/Git Yes, I have access. Now migration almost complete - I uploaded partial snapshot into git (snapshot of bering-uclibc4 tree), and updated buildtool logic to work with git. At least, buildtool.pl source linux works OK - so I expect no troubles. As I said, migration is trivial :) I added new paremeter for both server and source package - Repo, which contains pair project/repository (by default - leaf/leaf) - this will make multi-branch development easier. For completion I need that somebody push latest available snapshot into git with modified server names into packages (cvs-sourceforge is replaced by leaf-sourceforge, cvs4-sourceforge is replaced by leaf4-sourceforge and so on). I did this by shell command find . -name buildtool.cfg | xargs perl -i -p -e 's/cvs4-/leaf4-/g;s/cvs-/leaf-/g' into source tree, it may be inaccurate, but at 1st look it doesn't replace anything except server name. Charles, Are you familiar enough with git to accomplish this task? -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
01.02.2011 22:42, Mike Noyes пишет: On Tue, 2011-02-01 at 22:27 +0200, Andrew wrote: 01.02.2011 17:37, Mike Noyes пишет: On Tue, 2011-02-01 at 14:15 +0200, Andrew wrote: 01.02.2011 14:02, KP Kirchdoerfer пишет: Am Dienstag, 1. Februar 2011, um 12:45:00 schrieb Andrew: 31.01.2011 23:06, Mike Noyes пишет: Charles, I just enabled svn for our project again. Git is enabled also, but I suspect migration to git is more complex. I think that migration to any SCM is trivial till it's possible to get access to source tree (latest version of files) via HTTP. And gitweb provides this at 1st look. Link to latest revision of file path/filenamelooks like this: http://projectname.git.sourceforge.net/git/gitweb.cgi?p=path;a=blob_pla in;f=filename;hb=HEAD Latest versions should be possible, Charles rsync backup seems to be valid, I have the latest packages and sources in my local cvs copy, and finally SF should have a backup as well. IMHO non-trivial are the changes needed for buildtool (a new scm downloader is needed, the sources.cfg needs rework and probably every buildtool.mk file). Also we need to change the documentation, helper files like genpage.sh and maybe some more corner stuff. That's why I'd like to have a stable version first and move to a new SCM later, IF possible... kp Buildtool actually takes data from CVS via http. And it isn't too hard to modify ViewCVS.pm to take data from git via gitweb - like from CVS via viewvc. Everyone, My preference is a move to git, provided buildtool SCM transition is equal. The git community is dominating SCMs (see github). However, project member training (commands, distributed nature, etc.) is steeper than a move to SVN. +1 Git I propose Charles work on SVN and Andrew work on Git, so we can see what issues arise. This should allow our developers to make a decision on which SCM will serve our community best. Andrew, Please let me know if you have access to our git repository. https://sourceforge.net/apps/trac/sourceforge/wiki/Git Yes, I have access. Now migration almost complete - I uploaded partial snapshot into git (snapshot of bering-uclibc4 tree), and updated buildtool logic to work with git. At least, buildtool.pl source linux works OK - so I expect no troubles. As I said, migration is trivial :) I added new paremeter for both server and source package - Repo, which contains pair project/repository (by default - leaf/leaf) - this will make multi-branch development easier. For completion I need that somebody push latest available snapshot into git with modified server names into packages (cvs-sourceforge is replaced by leaf-sourceforge, cvs4-sourceforge is replaced by leaf4-sourceforge and so on). I did this by shell command find . -name buildtool.cfg | xargs perl -i -p -e 's/cvs4-/leaf4-/g;s/cvs-/leaf-/g' into source tree, it may be inaccurate, but at 1st look it doesn't replace anything except server name. Charles, Are you familiar enough with git to accomplish this task? This is quite easy: do git clone and set personal data (name/email); copy bering-uclibc/apps and bering-uclibc/contrib into git dir; modify config files (replace server names) into sources' buildenv.conf; do git add * and then do git commit and git push. After short look in leaf-commits mailing list, in current git snapshot only last busybox commit (update to 1.18.2) is missed. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] next steps
Hi; the beta2 version has about 140 downloads, which is a quite good number for just eight days, and no reports, which is even better - as the old saying goes no news are good news. IMHO the most pressing trac tickets for the next version are #8, #18 and probably #25. I'm lost how to fix these on my own, and I'm also facing some busy weeks ahead (hopefully a change of job as well), but I'm willing to free as much time as possible if testing, discusson and feedback is needed for those problems. I think we should concentrate on those cause, once they are solved, a stable version will be in sight. And it might be a good base, to make a step back and rework our infrastructure. This could be work on buildenv to support more platforms, or more possibly, we may be forced to move away from cvs I don't like to make, or be forced to make, such changes before we finally have a stable successor to Bering-uClibc 3.x. Opinions? kp BTW: I was a bit concerned using a wiki for documenation, cause a lot of wikis on the net are cluttered and somewhat useless. I believe both is definitly not true for the Bering-uClibc4 wiki - and compared to the earlier docbook stuff it's an improvement content-wise and even more to develop and maintain the documentation. A note to myself to not be too conservative has been made :) -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Mon, 2011-01-31 at 17:37 +0100, KP Kirchdoerfer wrote: -snip- And it might be a good base, to make a step back and rework our infrastructure. This could be work on buildenv to support more platforms, or more possibly, we may be forced to move away from cvs I don't like to make, or be forced to make, such changes before we finally have a stable successor to Bering-uClibc 3.x. KP, Maybe Charles or someone else with SVN experience is willing to step in and see what issues there are with our current CVS build environment on SVN. I suspect SF will be forced to discontinue CVS service for security reasons. This is one reason I've been pushing for us to migrate to git. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/31/2011 12:54 PM, Mike Noyes wrote: On Mon, 2011-01-31 at 17:37 +0100, KP Kirchdoerfer wrote: -snip- And it might be a good base, to make a step back and rework our infrastructure. This could be work on buildenv to support more platforms, or more possibly, we may be forced to move away from cvs I don't like to make, or be forced to make, such changes before we finally have a stable successor to Bering-uClibc 3.x. KP, Maybe Charles or someone else with SVN experience is willing to step in and see what issues there are with our current CVS build environment on SVN. I suspect SF will be forced to discontinue CVS service for security reasons. This is one reason I've been pushing for us to migrate to git. I play with subversion daily, administer a production subversion server as part of my day job, and have migrated several projects from a legacy cvs environment to subversion. If there's anything I can do to assist with a transition from cvs to svn, please let me know. - -- Charles Steinkuehler char...@steinkuehler.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1HFHsACgkQLywbqEHdNFwV+wCgwx2rUL0eTwC9pawzYvZ2pX4S VCEAoPQKEx3K+3TCXbFLaGkEztBcd2/R =k2Gw -END PGP SIGNATURE- -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Mon, 2011-01-31 at 13:58 -0600, Charles Steinkuehler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/31/2011 12:54 PM, Mike Noyes wrote: On Mon, 2011-01-31 at 17:37 +0100, KP Kirchdoerfer wrote: -snip- And it might be a good base, to make a step back and rework our infrastructure. This could be work on buildenv to support more platforms, or more possibly, we may be forced to move away from cvs I don't like to make, or be forced to make, such changes before we finally have a stable successor to Bering-uClibc 3.x. KP, Maybe Charles or someone else with SVN experience is willing to step in and see what issues there are with our current CVS build environment on SVN. I suspect SF will be forced to discontinue CVS service for security reasons. This is one reason I've been pushing for us to migrate to git. I play with subversion daily, administer a production subversion server as part of my day job, and have migrated several projects from a legacy cvs environment to subversion. If there's anything I can do to assist with a transition from cvs to svn, please let me know. Charles, I just enabled svn for our project again. Git is enabled also, but I suspect migration to git is more complex. SVN Admin https://sourceforge.net/project/admin/svn.php?group_id=13751 KP, Martin, Andrew, and the rest of the Bering team can provide you with migration issues. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/31/2011 3:06 PM, Mike Noyes wrote: SVN Admin https://sourceforge.net/project/admin/svn.php?group_id=13751 KP, Martin, Andrew, and the rest of the Bering team can provide you with migration issues. Thanks! What's the current status of subversion? Has any CVS content been migrated into SVN? If not, does SF have a process for this, or would I need to do it manually? If I need to migrate data from CVS, is there anything that would need to happen first (ie: any required cleanup or changes on the CVS side)? I tried browsing the subversion repository, and it didn't seem to work...I'm not sure if that's due to there being nothing there or a result of the recent security issues with SF. I should have a recent CVS tarball or archive, from prior to SF shutting things down. I can bring that online or use it to convert into subversion if necessary. - -- Charles Steinkuehler char...@steinkuehler.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1HJxgACgkQLywbqEHdNFxStgCg4qDHZSllRxyREWggza9TAzV6 T58AoLY1jesCIQvlNFSz2a9WcC9R2hMV =ub7u -END PGP SIGNATURE- -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] next steps
On Mon, 2011-01-31 at 15:18 -0600, Charles Steinkuehler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/31/2011 3:06 PM, Mike Noyes wrote: SVN Admin https://sourceforge.net/project/admin/svn.php?group_id=13751 KP, Martin, Andrew, and the rest of the Bering team can provide you with migration issues. Thanks! What's the current status of subversion? Has any CVS content been migrated into SVN? If not, does SF have a process for this, or would I need to do it manually? Charles, I believe the SF documentation linked below should walk you through migration. https://sourceforge.net/apps/trac/sourceforge/wiki/Using%20rsync%20for%20backups https://sourceforge.net/apps/trac/sourceforge/wiki/CVS%20adminrepo https://sourceforge.net/apps/trac/sourceforge/wiki/SVN%20adminrepo#ImportingfromotherreposincludingotherSCMs If I need to migrate data from CVS, is there anything that would need to happen first (ie: any required cleanup or changes on the CVS side)? There were some cleanup actions requested by our project members. I haven't attended to them with adminrepo. I tried browsing the subversion repository, and it didn't seem to work...I'm not sure if that's due to there being nothing there or a result of the recent security issues with SF. I suspect your first premise is correct. I should have a recent CVS tarball or archive, from prior to SF shutting things down. I can bring that online or use it to convert into subversion if necessary. I think an rsync of the doc and bering-uclibc trees are all that are necessary for migration. We can archive the rest, as it's legacy now. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
