Menu
▾
▴
phpwebsite-developers
|
From: Adam M. <ad...@tu...> - 2003-02-10 17:36:03
|
Just an fyi...we will be restructuring our cvs repository this afternoon. If you actively use code from our cvs repository, you will need to wait til the restructuring is complete to continue. Once the restructuring is done, anyone who is running a cvs copy of phpwebsite should remove their code and re-checkout everything. There may be some version history losses in the transfer, we will be archiving old history as much as we can. I will be sure to post as soon as we are done here. Thanks Adam --------------------------------------------------------------------- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Mike N. <mh...@us...> - 2003-02-10 17:50:07
|
On Mon, 2003-02-10 at 09:47, Adam Morton wrote: > > Just an fyi...we will be restructuring our cvs repository this afternoon. > If you actively use code from our cvs repository, you will need to wait > til the restructuring is complete to continue. Once the restructuring is > done, anyone who is running a cvs copy of phpwebsite should remove their > code and re-checkout everything. There may be some version history losses > in the transfer, we will be archiving old history as much as we can. > > I will be sure to post as soon as we are done here. Adam, Let me guess. You'll rename phpwebsite to phpwebsite_0.8. Then you're going to move phpwebsite_core to phpwebsite. Then move phpwebsite_modules to phpwebsite/mod. Then move phpwebsite_themes to phpwebsite/themes. After this is done you'll create modules in CVSROOT for core, mod, and themes. How did I do? ref. C.1 The modules file http://www.cvshome.org/docs/manual/cvs_18.html#SEC157 -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
|
From: Adam M. <ad...@tu...> - 2003-02-10 18:15:35
|
Close but we're ripping out the old code all together, modules will each have their own repository and the core will have it's own named 'phpwebsite'. All themes will go into the 'themes' repository. Adam > On Mon, 2003-02-10 at 09:47, Adam Morton wrote: >> >> Just an fyi...we will be restructuring our cvs repository this >> afternoon. If you actively use code from our cvs repository, you will >> need to wait til the restructuring is complete to continue. Once the >> restructuring is done, anyone who is running a cvs copy of phpwebsite >> should remove their code and re-checkout everything. There may be >> some version history losses in the transfer, we will be archiving old >> history as much as we can. >> >> I will be sure to post as soon as we are done here. > > Adam, > Let me guess. > > You'll rename phpwebsite to phpwebsite_0.8. Then you're going to move > phpwebsite_core to phpwebsite. Then move phpwebsite_modules to > phpwebsite/mod. Then move phpwebsite_themes to phpwebsite/themes. After > this is done you'll create modules in CVSROOT for core, mod, and themes. > > How did I do? > > ref. C.1 The modules file > http://www.cvshome.org/docs/manual/cvs_18.html#SEC157 > > -- > Mike Noyes <mhnoyes @ users.sourceforge.net> > http://sourceforge.net/users/mhnoyes/ > http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers --------------------------------------------------------------------- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Mike N. <mh...@us...> - 2003-02-10 18:26:37
|
On Mon, 2003-02-10 at 10:27, Adam Morton wrote: > Close but we're ripping out the old code all together, modules will each > have their own repository and the core will have it's own named > 'phpwebsite'. All themes will go into the 'themes' repository. Adam, Before removing the old 'phpwebsite' module/tree, please tarball it. Then upload it to the SF FRS (file release system). This will provide a last known source for the 0.8x code. https://sourceforge.net/project/showfiles.php?group_id=15539 SourceForge.net: G4. Guide to the File Release System (FRS) https://sourceforge.net/docman/display_doc.php?docid=6445&group_id=1 -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
|
From: Adam M. <ad...@tu...> - 2003-02-10 18:44:32
|
We decided to keep the current 0.8.x code in the repository. We will make up a tarball of the most recent 0.8.x code and post it to sourceforge as well. Adam > On Mon, 2003-02-10 at 10:27, Adam Morton wrote: >> Close but we're ripping out the old code all together, modules will >> each have their own repository and the core will have it's own named >> 'phpwebsite'. All themes will go into the 'themes' repository. > > Adam, > Before removing the old 'phpwebsite' module/tree, please tarball it. > Then upload it to the SF FRS (file release system). This will provide a > last known source for the 0.8x code. > > https://sourceforge.net/project/showfiles.php?group_id=15539 > > SourceForge.net: G4. Guide to the File Release System (FRS) > https://sourceforge.net/docman/display_doc.php?docid=6445&group_id=1 > > -- > Mike Noyes <mhnoyes @ users.sourceforge.net> > http://sourceforge.net/users/mhnoyes/ > http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers --------------------------------------------------------------------- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Adam M. <ad...@tu...> - 2003-02-10 19:41:02
Attachments:
build_phpws.sh
|
OK All the changes are complete. We are still setting up users and groups, however so only anonymous check outs are active at the moment. I wrote a shell script that will remotely checkout and build a phpwebsite installation for you. Make sure you edit the settings at the top to reflect the directory you want the installation to go into and the username on the remote string if you are not doing an anonymous checkout. You can also tweak which modules you wish to have installed. The secure_phpws script is run at the end as a non root user for setup. So make sure to fix your permissions after you run the web based installer. I will be submitting the script to CVS as well in the shellscripts repository. Enjoy! Adam > We decided to keep the current 0.8.x code in the repository. We will > make up a tarball of the most recent 0.8.x code and post it to > sourceforge as well. > > Adam > >> On Mon, 2003-02-10 at 10:27, Adam Morton wrote: >>> Close but we're ripping out the old code all together, modules will >>> each have their own repository and the core will have it's own named >>> 'phpwebsite'. All themes will go into the 'themes' repository. >> >> Adam, >> Before removing the old 'phpwebsite' module/tree, please tarball it. >> Then upload it to the SF FRS (file release system). This will provide >> a last known source for the 0.8x code. >> >> https://sourceforge.net/project/showfiles.php?group_id=15539 >> >> SourceForge.net: G4. Guide to the File Release System (FRS) >> https://sourceforge.net/docman/display_doc.php?docid=6445&group_id=1 >> >> -- >> Mike Noyes <mhnoyes @ users.sourceforge.net> >> http://sourceforge.net/users/mhnoyes/ >> http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ >> >> >> >> >> ------------------------------------------------------- >> This SF.NET email is sponsored by: >> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! >> http://www.vasoftware.com >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > --------------------------------------------------------------------- > Adam Morton > Developer - Electronic Student Services > http://phpwebsite.appstate.edu > Founder - Appalachian Linux Users Group > http://alug.appstate.edu > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers --------------------------------------------------------------------- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Matthew M. <ma...@tu...> - 2003-02-11 12:58:14
|
> I wrote a shell script that will remotely checkout and build a > phpwebsite installation for you. Daddy like. Matt |
|
From: Mike N. <mh...@us...> - 2003-02-24 19:21:21
|
On Mon, 2003-02-10 at 11:52, Adam Morton wrote:
> I wrote a shell script that will remotely checkout and build a phpwebsite
> installation for you. Make sure you edit the settings at the top to
> reflect the directory you want the installation to go into and the
> username on the remote string if you are not doing an anonymous checkout.
> You can also tweak which modules you wish to have installed. The
> secure_phpws script is run at the end as a non root user for setup. So
> make sure to fix your permissions after you run the web based installer.
Adam,
I have a diff for your shell script. Instead of checking out modules it
exports them based on tags. This will allow developers to work from
known tag points, and avoids the unnecessary CVS directory clutter
checkout creates.
$ diff -u ~/leaf/phpwebsite/build_phpws.sh ~/bin/build_phpws.sh
--- /home/mhnoyes/leaf/phpwebsite/build_phpws.sh Mon Feb 24 09:22:19
2003+++ /home/mhnoyes/bin/build_phpws.sh Mon Feb 24 11:00:25 2003
@@ -27,25 +27,28 @@
# Themes to check out
THEMES="AHP clean Default gax mainsite shiny winxp"
+# Tag to retrieve from repository
+TAG=HEAD
+
################################################
# END SETTINGS: Do not edit beyond this line!! #
################################################
# Grab the phpwebsite core and core modules
-cvs $REMOTE co phpwebsite
+cvs $REMOTE -q ex -r"$TAG" phpwebsite
for i in $CORE_MODULES; do
- cvs $REMOTE co $i
+ cvs $REMOTE -q ex -r"$TAG" $i
mv $i phpwebsite/mod/
done
# Grab any extra modules the user wants
for i in $OTHER_MODULES; do
- cvs $REMOTE co $i
+ cvs $REMOTE -q ex -r"$TAG" $i
mv $i phpwebsite/mod/
done
# Check out all themes and pick each one out individually
-cvs $REMOTE co themes
+cvs $REMOTE -q ex -r"$TAG" themes
for i in $THEMES; do
mv themes/$i phpwebsite/themes/
done
--
Mike Noyes <mhnoyes @ users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/
|
|
From: Don S. <do...@se...> - 2003-02-24 19:42:25
|
+1 to tags. Also I would like to see the script download and untar the pear tarball at http://phpwebsite.appstate.edu/downloads/pear/pear.current.tar.gz . Then delete the tarball once unpacked. Maybe have it do this if the user passes "--with-pear" to the build_phpws.sh script. Don. On Mon, 24 Feb 2003, Mike Noyes wrote: > On Mon, 2003-02-10 at 11:52, Adam Morton wrote: > > I wrote a shell script that will remotely checkout and build a phpwebsite > > installation for you. Make sure you edit the settings at the top to > > reflect the directory you want the installation to go into and the > > username on the remote string if you are not doing an anonymous checkout. > > You can also tweak which modules you wish to have installed. The > > secure_phpws script is run at the end as a non root user for setup. So > > make sure to fix your permissions after you run the web based installer. > > Adam, > I have a diff for your shell script. Instead of checking out modules it > exports them based on tags. This will allow developers to work from > known tag points, and avoids the unnecessary CVS directory clutter > checkout creates. > > > $ diff -u ~/leaf/phpwebsite/build_phpws.sh ~/bin/build_phpws.sh > --- /home/mhnoyes/leaf/phpwebsite/build_phpws.sh Mon Feb 24 09:22:19 > 2003+++ /home/mhnoyes/bin/build_phpws.sh Mon Feb 24 11:00:25 2003 > @@ -27,25 +27,28 @@ > # Themes to check out > THEMES="AHP clean Default gax mainsite shiny winxp" > > +# Tag to retrieve from repository > +TAG=HEAD > + > ################################################ > # END SETTINGS: Do not edit beyond this line!! # > ################################################ > > # Grab the phpwebsite core and core modules > -cvs $REMOTE co phpwebsite > +cvs $REMOTE -q ex -r"$TAG" phpwebsite > for i in $CORE_MODULES; do > - cvs $REMOTE co $i > + cvs $REMOTE -q ex -r"$TAG" $i > mv $i phpwebsite/mod/ > done > > # Grab any extra modules the user wants > for i in $OTHER_MODULES; do > - cvs $REMOTE co $i > + cvs $REMOTE -q ex -r"$TAG" $i > mv $i phpwebsite/mod/ > done > > # Check out all themes and pick each one out individually > -cvs $REMOTE co themes > +cvs $REMOTE -q ex -r"$TAG" themes > for i in $THEMES; do > mv themes/$i phpwebsite/themes/ > done > > > |
|
From: Adam M. <ad...@tu...> - 2003-02-24 21:46:55
|
ok guys, I will post my other script called 'ballz' to the cvs repository this evening. It does everything through anonymous exports and can build a tarball of any module requested or the entire phpwebsite installation, including the pear libs. Let me know what you think :) Adam > +1 to tags. > > Also I would like to see the script download and untar the pear tarball > at http://phpwebsite.appstate.edu/downloads/pear/pear.current.tar.gz . > Then delete the tarball once unpacked. Maybe have it do this if the > user passes "--with-pear" to the build_phpws.sh script. > > Don. > > On Mon, 24 Feb 2003, Mike Noyes wrote: > >> On Mon, 2003-02-10 at 11:52, Adam Morton wrote: >> > I wrote a shell script that will remotely checkout and build a >> phpwebsite installation for you. Make sure you edit the settings at >> the top to reflect the directory you want the installation to go >> into and the username on the remote string if you are not doing an >> anonymous checkout. You can also tweak which modules you wish to >> have installed. The secure_phpws script is run at the end as a non >> root user for setup. So make sure to fix your permissions after you >> run the web based installer. >> >> Adam, >> I have a diff for your shell script. Instead of checking out modules >> it exports them based on tags. This will allow developers to work from >> known tag points, and avoids the unnecessary CVS directory clutter >> checkout creates. >> >> >> $ diff -u ~/leaf/phpwebsite/build_phpws.sh ~/bin/build_phpws.sh >> --- /home/mhnoyes/leaf/phpwebsite/build_phpws.sh Mon Feb 24 09:22:19 >> 2003+++ /home/mhnoyes/bin/build_phpws.sh Mon Feb 24 11:00:25 2003 @@ >> -27,25 +27,28 @@ >> # Themes to check out >> THEMES="AHP clean Default gax mainsite shiny winxp" >> >> +# Tag to retrieve from repository >> +TAG=HEAD >> + >> ################################################ >> # END SETTINGS: Do not edit beyond this line!! # >> ################################################ >> >> # Grab the phpwebsite core and core modules >> -cvs $REMOTE co phpwebsite >> +cvs $REMOTE -q ex -r"$TAG" phpwebsite >> for i in $CORE_MODULES; do >> - cvs $REMOTE co $i >> + cvs $REMOTE -q ex -r"$TAG" $i >> mv $i phpwebsite/mod/ >> done >> >> # Grab any extra modules the user wants >> for i in $OTHER_MODULES; do >> - cvs $REMOTE co $i >> + cvs $REMOTE -q ex -r"$TAG" $i >> mv $i phpwebsite/mod/ >> done >> >> # Check out all themes and pick each one out individually >> -cvs $REMOTE co themes >> +cvs $REMOTE -q ex -r"$TAG" themes >> for i in $THEMES; do >> mv themes/$i phpwebsite/themes/ >> done >> >> >> > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers --------------------------------------------------------------------- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Matthew M. <ma...@tu...> - 2003-02-24 21:57:35
|
> ok guys, I will post my other script called 'ballz' to the cvs > repository this evening. It does everything through anonymous exports > and can build a tarball of any module requested or the entire phpwebsite > installation, including the pear libs. Let me know what you think :) This script is a gift from Olympus. Please test it out and grab today's CVS. We would like to release a final cut tomorrow if no bugs are experienced. Thanks, Matt -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu > > Adam > >> +1 to tags. >> >> Also I would like to see the script download and untar the pear >> tarball at >> http://phpwebsite.appstate.edu/downloads/pear/pear.current.tar.gz . >> Then delete the tarball once unpacked. Maybe have it do this if the >> user passes "--with-pear" to the build_phpws.sh script. >> >> Don. >> >> On Mon, 24 Feb 2003, Mike Noyes wrote: >> >>> On Mon, 2003-02-10 at 11:52, Adam Morton wrote: >>> > I wrote a shell script that will remotely checkout and build a >>> phpwebsite installation for you. Make sure you edit the settings at >>> the top to reflect the directory you want the installation to go into >>> and the username on the remote string if you are not doing an >>> anonymous checkout. You can also tweak which modules you wish to >>> have installed. The secure_phpws script is run at the end as a non >>> root user for setup. So make sure to fix your permissions after you >>> run the web based installer. >>> >>> Adam, >>> I have a diff for your shell script. Instead of checking out modules >>> it exports them based on tags. This will allow developers to work >>> from known tag points, and avoids the unnecessary CVS directory >>> clutter checkout creates. >>> >>> >>> $ diff -u ~/leaf/phpwebsite/build_phpws.sh ~/bin/build_phpws.sh --- >>> /home/mhnoyes/leaf/phpwebsite/build_phpws.sh Mon Feb 24 09:22:19 >>> 2003+++ /home/mhnoyes/bin/build_phpws.sh Mon Feb 24 11:00:25 2003 @@ >>> -27,25 +27,28 @@ >>> # Themes to check out >>> THEMES="AHP clean Default gax mainsite shiny winxp" >>> >>> +# Tag to retrieve from repository >>> +TAG=HEAD >>> + >>> ################################################ >>> # END SETTINGS: Do not edit beyond this line!! # >>> ################################################ >>> >>> # Grab the phpwebsite core and core modules >>> -cvs $REMOTE co phpwebsite >>> +cvs $REMOTE -q ex -r"$TAG" phpwebsite >>> for i in $CORE_MODULES; do >>> - cvs $REMOTE co $i >>> + cvs $REMOTE -q ex -r"$TAG" $i >>> mv $i phpwebsite/mod/ >>> done >>> >>> # Grab any extra modules the user wants >>> for i in $OTHER_MODULES; do >>> - cvs $REMOTE co $i >>> + cvs $REMOTE -q ex -r"$TAG" $i >>> mv $i phpwebsite/mod/ >>> done >>> >>> # Check out all themes and pick each one out individually >>> -cvs $REMOTE co themes >>> +cvs $REMOTE -q ex -r"$TAG" themes >>> for i in $THEMES; do >>> mv themes/$i phpwebsite/themes/ >>> done >>> >>> >>> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > --------------------------------------------------------------------- > Adam Morton > Developer - Electronic Student Services > http://phpwebsite.appstate.edu > Founder - Appalachian Linux Users Group > http://alug.appstate.edu > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
|
From: Mike N. <mh...@us...> - 2003-02-24 22:35:18
|
On Mon, 2003-02-24 at 14:09, Matthew McNaney wrote:
> > ok guys, I will post my other script called 'ballz' to the cvs
> > repository this evening. It does everything through anonymous exports
> > and can build a tarball of any module requested or the entire phpwebsite
> > installation, including the pear libs. Let me know what you think :)
>
> This script is a gift from Olympus. Please test it out and grab today's
> CVS. We would like to release a final cut tomorrow if no bugs are
> experienced.
Matt,
I just tested the 'ballz' script with $1=full $2=0.9.0. It worked like a
charm. :-)
Adam,
I see you caught my mistake. I forgot that export prunes empty
directories. The correction to my earlier diff for build_phpws.sh is
below.
# Grab the phpwebsite core and core modules
-cvs $REMOTE co phpwebsite
+cvs $REMOTE -q ex -r $TAG phpwebsite
+mkdir phpwebsite/mod
+mkdir phpwebsite/themes
for i in $CORE_MODULES; do
--
Mike Noyes <mhnoyes @ users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/
|
|
From: <ad...@tu...> - 2003-03-14 16:29:28
|
Mike, Bringing up old school stuff...I am updating some stuff in the build_phpws.sh file and I was going to add your diff to the file. I just have a couple of questions. Is this command a checkout or an export? cvs $REMOTE -q ex -r"$TAG" phpwebsite If it's an export, I'm not sure this method will work in this particular script since it is meant to build the most recent cvs copy of phpwebsite, themes, and modules with the expectation that the developer will be updating that code and later commit it. And will the developer be protected from checking out from a particular tag point and then later commiting their code and accidentally having old code from that tag point overwrite new code that is most recent in cvs? Also what does the tag 'HEAD' mean? :) Adam > Adam, > I have a diff for your shell script. Instead of checking out modules it > exports them based on tags. This will allow developers to work from > known tag points, and avoids the unnecessary CVS directory clutter > checkout creates. > > > $ diff -u ~/leaf/phpwebsite/build_phpws.sh ~/bin/build_phpws.sh > --- /home/mhnoyes/leaf/phpwebsite/build_phpws.sh Mon Feb 24 09:22:19 > 2003+++ /home/mhnoyes/bin/build_phpws.sh Mon Feb 24 11:00:25 2003 > @@ -27,25 +27,28 @@ > # Themes to check out > THEMES="AHP clean Default gax mainsite shiny winxp" > > +# Tag to retrieve from repository > +TAG=HEAD > + > ################################################ > # END SETTINGS: Do not edit beyond this line!! # > ################################################ > > # Grab the phpwebsite core and core modules > -cvs $REMOTE co phpwebsite > +cvs $REMOTE -q ex -r"$TAG" phpwebsite > for i in $CORE_MODULES; do > - cvs $REMOTE co $i > + cvs $REMOTE -q ex -r"$TAG" $i > mv $i phpwebsite/mod/ > done > > # Grab any extra modules the user wants > for i in $OTHER_MODULES; do > - cvs $REMOTE co $i > + cvs $REMOTE -q ex -r"$TAG" $i > mv $i phpwebsite/mod/ > done > > # Check out all themes and pick each one out individually > -cvs $REMOTE co themes > +cvs $REMOTE -q ex -r"$TAG" themes > for i in $THEMES; do > mv themes/$i phpwebsite/themes/ > done > > > -- > Mike Noyes <mhnoyes @ users.sourceforge.net> > http://sourceforge.net/users/mhnoyes/ > http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > --------------------------------------------------------------------- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Mike N. <mh...@us...> - 2003-03-14 17:01:47
|
On Fri, 2003-03-14 at 08:33, ad...@tu... wrote: > Bringing up old school stuff...I am updating some stuff in the > build_phpws.sh file and I was going to add your diff to the file. I just > have a couple of questions. Adam, I hope I'm able to answer them. :) > Is this command a checkout or an export? > > cvs $REMOTE -q ex -r"$TAG" phpwebsite export = exp = ex > If it's an export, I'm not sure this method will work in this particular > script since it is meant to build the most recent cvs copy of phpwebsite, > themes, and modules with the expectation that the developer will be > updating that code and later commit it. Then I misinterpreted the intent of the script. An export contains no CVS control files, and is not a functional working copy of the repository module. > And will the developer be protected from checking out from a particular > tag point and then later commiting their code and accidentally having old > code from that tag point overwrite new code that is most recent in cvs? A developer wont be able to use an export to commit changes. It's not a working copy. > Also what does the tag 'HEAD' mean? :) HEAD is a "symbolic tag" usually associated with the most recent version of all files in a repository module. The other way to export the most current files from a cvs module is to use date with timezone. The timezone is necessary because cvs assumes local TZ when performing operations. Obviously this can lead to exports that are up to 24 hours old. I use the following string for date exports: DATE=`date '+%Y-%m-%d %T %Z'` -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
|
From: Mike N. <mh...@us...> - 2003-03-14 17:17:32
|
On Fri, 2003-03-14 at 09:02, Mike Noyes wrote:
> On Fri, 2003-03-14 at 08:33, ad...@tu... wrote:
> > And will the developer be protected from checking out from a particular
> > tag point and then later commiting their code and accidentally having old
> > code from that tag point overwrite new code that is most recent in cvs?
>
> A developer wont be able to use an export to commit changes. It's not a
> working copy.
Adam,
Here are some additional resources that explain the 'benefits of/uses
for' tags.
cvshome.org: "More about branching and tagging"
http://www.cvshome.org/docs/manual/cvs_4.html#SEC48
The Cederqvist Manual: "Branches"
http://www.gnu.org/manual/cvs/html_chapter/cvs_8.html#SEC50
Open Source Development with CVS:
"Marking A Moment In Time (Tags)" "Branches"
http://cvsbook.red-bean.com/cvsbook.html#Marking_A_Moment_In_Time__Tags_
http://cvsbook.red-bean.com/cvsbook.html#Branches
--
Mike Noyes <mhnoyes @ users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/
|
|
From: <ad...@tu...> - 2003-03-14 17:26:13
|
Mike, Thanks for all the info! It is very helpful. I will look into making the TAG changes in the 'ballz' script instead. That script is intended to create tarballs of the full phpwebsite install or any piece therein. Adding tag support to that script would make it more flexible and powerful. Adam > On Fri, 2003-03-14 at 09:02, Mike Noyes wrote: >> On Fri, 2003-03-14 at 08:33, ad...@tu... wrote: >> > And will the developer be protected from checking out from a >> particular >> > tag point and then later commiting their code and accidentally having >> old >> > code from that tag point overwrite new code that is most recent in >> cvs? >> >> A developer wont be able to use an export to commit changes. It's not a >> working copy. > > Adam, > Here are some additional resources that explain the 'benefits of/uses > for' tags. > > cvshome.org: "More about branching and tagging" > http://www.cvshome.org/docs/manual/cvs_4.html#SEC48 > > The Cederqvist Manual: "Branches" > http://www.gnu.org/manual/cvs/html_chapter/cvs_8.html#SEC50 > > Open Source Development with CVS: > "Marking A Moment In Time (Tags)" "Branches" > http://cvsbook.red-bean.com/cvsbook.html#Marking_A_Moment_In_Time__Tags_ > http://cvsbook.red-bean.com/cvsbook.html#Branches > > -- > Mike Noyes <mhnoyes @ users.sourceforge.net> > http://sourceforge.net/users/mhnoyes/ > http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ > > > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X