[Typo3-debian] Integration of Typo3-Packages into the Debian main archive

[Michael Stucki]

Hello Christian & all the rest,

> It's fine for me (now). After some more private email with Michael and
> rethinking the whole discussion, I slowly realize the facts you stated
> above. I've underestimated the effort needed to do a useful split. I've
> already reacted and undo the split. The new packages are now available
> through http://users.oche.de/~leutloff/debian/packages/

Thanks for finally accepting this. I sent a mail to Kasper last week because
I was really interested to know if there are problems when removing typo3/.

This is his reply and it just confirms that your decision was right! :-)

--- cut ---
Subject: Re: Debian packages, need your advice
Date: Freitag, 26. November 2004 11.18
From: Kasper Skårhøj <kasper2004 at typo3.com>
To: Michael Stucki <michael at typo3.org>

Hi Michael,


thanks for asking me,

On Mon, 2004-11-22 at 13:10, Michael Stucki wrote:
> Hi Kasper,
>
> there is a guy, Christian Leutloff, who wants to maintain Debian packages
> of TYPO3. I like this and he really did some nice work already. But there
> are some conflicts, he has different plans than I had with my previous
> packages, so I ask you to take some minutes for helping me in this
> matter...
>
> Short summary: Christian has plans where I do not agree because I don't
> trust that this won't break anything.
>
> 1.) Split up the package into two parts:
> - typo3-src-fe (everything except typo3/)
> - typo3-src-be (typo3/)
>
>
> What I know is that this will definitely break all global/system
> extensions. But what about the rest? What if an extension tries to use
> anything from the typo3/ directory? Can we be sure this is not the case?

No, extensions DOES use stuff from typo3/ I suppose. I think it is a
very bad idea to separate these. I don't see the point either. Why does
he want to do that? What should the advantage be?

> My solution was different but definitely more stable: Just add a die()
> command on top of typo3/index.php.

Oh, so he just wants to disable the backend? Well, I have thought about
that before and I have concluded that you cannot safely separate teh
typo3/ dir from the frontend! So it will not work.

I rather like to look at other solutions for shutting down the backend.
One is already at hand; In TYPO3_CONF_VARS you can shut down the backend
totally with a flag.

> 2.) Automatic database updates, e.g. update from TYPO3 3.7.0 to 3.8.0.
>
> My argumentation is that he can do automatic updates for one branch
> (patch-updates) but NOT for any minor updates!
>
> Within 3.7.x he can be sure that there will be no database changes but in
> version 3.8.0 there will most likely be updates, and these updates will
> need user interaction if there is a conflict.
>
> Generally I think that branch updates are not that easy in TYPO3, you can
> not be sure that it won't break anything. That's why I have suggested to
> create packages for each branch:
> - typo3-src-3-7
> - typo3-src-3-8
> - etc.
>
> What do you think?

Go with your intuition; Don't.

> Well, I would be happy to get some arguments from you.

As for separating frontend and backend I can safely say, don't do it. As
for the rest I have to know more about the reasons why etc. But I don't
want to spend so much time on this so I trust you for that.

- kasper
--- cut ---

Thank you. Kind regards
- michael
-- 
Want support? Please read the list rules first: http://typo3.org/1438.0.html