[Typo3-dev] bugfixes - how to update 3.6.0 ???
Rene Suthoelder
t3 at 1zu6-design.de
Wed May 12 10:40:24 CEST 2004
well, in fact i found a "smart" solution supported by the more recent
windows os releases.
on those operating systems - they have to support NTFS - it is in fact
possible to have symlinks for folders (NOT single files).
microsoft calls these symlinks junctions and there are at least 2 user tools
to create such junctions.
the one is called linkd.exe and is part of the windows 2000 ressource kit.
therefore it is not free (correct me if i'm wrong). the other one is called
junction.exe and may be downloaded and used for free. it can be found on the
Sysinternal's website (http://www.sysinternals.com/ntw2k/source/misc.shtml).
one drawback: the windows explorer is not aware of junctions, they are
displayed like normal files. in each directory where i have junctions i put
a file named "JUNCTION LINKS IN HERE!!!!" to make sure that i use the
explorer carefull. if you want to see which files are junctions, you have to
use the shell like this
D:\www\sites\ > DIR typo3_*
Directory D:\WWW\sites
05.05.2004 12:38 <JUNCTION> typo3_src
05.05.2004 13:17 <DIR> typo3_src-3.6.0
29.04.2004 13:51 <DIR> typo3_src-3.6.0RC2
11.05.2004 21:27 <DIR> typo3_src-3.6.0RC2backup
11.05.2004 20:45 <DIR> typo3_src-3.6.1
0 Datei(en) 0 Bytes
D:\WWW\sites\ > JUNCTION.EXE -s
Junction v1.03 - Win2K junction creator and reparse point viewer
D:\WWW\sites\typo3_src: JUNCTION
Substitute Name: D:\WWW\sites\typo3_src-3.6.0
D:\WWW\sites\dav.elgato.inc\media: JUNCTION
Print Name : D:\WWW\sites\dav\tslib\media
Substitute Name: D:\WWW\sites\dav\tslib\media
as you see: this is pretty much the same as on unix (not really =:o).
i have prepared a dos batch file which i use to create those links. some
files have to be copied around (index.php, the font 2 files), but this is
handled by the script as well.
microsoft os'es that support NTFS
Windows NT (Workstation and Server) with latest Service Pack
Windows 2000 (Prefessional and Server) SP2
Windows 2003 Server
Windows XP (Home and Professional)
greets
rene
"Kasper Skårhøj" <kasper at typo3.com> schrieb im Newsbeitrag
news:mailman.2222.1084349993.256.typo3-dev at lists.netfielders.de...
> TER is not a good vehicle for transporting anything but single
> extensions. The reason why many of the global extensions has not been
> updated is because it would take me too long because it is slow and
> there are 70 of them - that would be two hours. Long time for me.
>
> CVS will be the method to go in the future. This is also what a new code
> structure will support (I will present this soon). Therefore I will not
> discuss the global extensions in further detail from now since that will
> quickly be an obsolete discussion.
>
> However, one problem remains for windows users: Even if you manage to
> set up a CVS client on windows (which is possible) you still have to
> cope with the redundacies of the code. For instance t3lib/ is found two
> places redundantly, tslib/ the same, index.php must be the same as
> tslib/index_ts.php and gfx/ is found three places as well as thumbs.php.
> On Unix this is no problem because we have symlinks. On windows you need
> to manually copy this around. Of course it would be nice if we could
> just remove this redundancy. This may be a long term solution but not an
> option here and now.
>
> What would be great was if someone could create a little tool on windows
> which will make the necessary duplicates of files after doing a CVS
> checkout on windows. Anyone?
>
>
>
> On Wed, 2004-05-12 at 00:20, Rene Suthoelder wrote:
> > well, my preferred patch tool would be the windows explorer, i.e. simply
> > copy the new, debugged/updated files to the folders they belong to.
> >
> > sorry for using the "reserved" word patch, which - you are absolutly
right -
> > in this dev-list context would mean a modification to an existing file
(thus
> > only altering its content, not replacing it).
> >
> > as stated earlier, i'm just a dumb enduser (and therefor perhaps not in
the
> > right list). perhaps my view on development issues differs a bit from
the
> > developers since i'm "only" interested in the result.
> >
> > but as a concerned enduser i started this thread to get the information
how
> > discovered bugfixes could go into my typo3 installation.
> >
> > at first i thought:
> >
> > 1. hey, there is the TER, just check the shy extensions for increased
> > version numbers and simply update the core (was 3.6.0RC1). this went
_badly_
> > wrong, leaving the whole installation unusable.
> > 2. then official 3.6.0 was released. ok, i did a reinstall with that
> > version.
> > 3. then reported bugs from the bugs.typo3.org were fixed and patches
were
> > available as seperate downloads and i didn't found them in TER nor in an
> > increased version number. ingmar wrote, that those minor changes would
never
> > be reflected in increased patch version numbers (major.minor.patch).
> > 4. then 3.6.1 was released and left me _totally_ confused...
> >
> > you see: for a user it can be very challenging to keep up with
development.
> > but as ingmar suggested
> >
> > > Just grab the 3.6 branch from CVS and you'll always get the latest
> > > bug-fixed 3.6.x version.
> >
> > i think this is the way to follow the next few months.
> >
> > just one last thought on that:
> >
> > couldn't the extension manager and TER be used to handle those update
> > issues? at first i thought this IS the tool to update the whole typo3
suite
> > (not "only" extensions).
> >
> > let's assume within a a given major version (example 3.x) you download a
> > basic source installation. the included extension manager could be told
to
> > _only_ update core and extensions for that major version (thus avoiding
> > incompatibility issues with extensions based on other core files as it
is
> > today).
> > once developers decide to release a new major version, you either
download
> > the new basic source installation (like you have to do today) or there
is
> > some upgrade flag in the typo3 basic install tool which allows the
system to
> > always update whatever is new.
> >
> > the point would be that you would have a clear breakpoint in your typo3
> > installation history telling you: new major version, stop, basic things
have
> > changed, new core features may have been added, old extension perhaps
have
> > been become obsolete etc. etc.
> > incompatabilities (remember the newloginbox hazzle when people used the
> > latest extension version which was incompatibel which the latest typo3
core)
> > could be avoided since - by rule - extensions have to be based on a
stable,
> > constantly bugfixed core.
> >
> > i hope it became clear what i mean =:o)
> >
> > rene
> >
> >
> >
> > "Michael Stucki" <mundaun at gmx.ch> schrieb im Newsbeitrag
> > news:mailman.1.1084308742.28593.typo3-dev at lists.netfielders.de...
> > > Hi Rene,
> > >
> > > > but from my point of view it is a pity that one has to reinstall the
> > whole
> > > > source package again (i use a win server for development and target
> > > > servers with various other OS'es on them).
> > >
> > > Maybe I will create patchsets later, but they will be non-official.
But is
> > > there anybody out who's using Windows and know about the patch
> > > program?! ;-)
> > >
> > > - michael
> > > --
> > > Want support? Please read the list rules first:
> > http://typo3.org/1438.0.html
> >
> >
> > _______________________________________________
> > Typo3-dev mailing list
> > Typo3-dev at lists.netfielders.de
> > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
> --
> God bless
>
> - kasper
>
> ------
>
> "To succeed in life, you need two things: ignorance and confidence." -
> Mark Twain.
>
>
More information about the TYPO3-dev
mailing list