incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus (OOo)" <marcus.m...@wtnet.de>
Subject Re: [RELEASE]: proposed directory structure on dist
Date Wed, 02 May 2012 20:27:26 GMT
Am 05/02/2012 08:54 AM, schrieb Jürgen Schmidt:
> On 5/2/12 12:23 AM, Marcus (OOo) wrote:
>> Am 05/01/2012 11:09 PM, schrieb Juergen Schmidt:
>>> On Tuesday, 1. May 2012 at 22:11, Marcus (OOo) wrote:
>>>> Am 05/01/2012 08:23 PM, schrieb Jürgen Schmidt:
>>>>> On 4/30/12 11:16 PM, Kay Schenk wrote:
>>>>>>
>>>>>>
>>>>>> On 04/30/2012 12:47 PM, Roberto Galoppini wrote:
>>>>>>> On Mon, Apr 30, 2012 at 8:47 PM, Marcus (OOo)<marcus.mail@wtnet.de>
>>>>>>> wrote:
>>>>>>>> Am 04/30/2012 07:00 PM, schrieb Rob Weir:
>>>>>>>>
>>>>>>>>> On Mon, Apr 30, 2012 at 12:44 PM, Kay Schenk<kay.schenk@gmail.com>
>>>>>>>>> �wrote:
>>>>>>>>>
>>>>>>>>> <snip>
>>>>>>>>>
>>>>>>>>>> Right now I have the DL friendly script setup to
only use
>>>>>>>>>> SF...which is
>>>>>>>>>> setup in the "old" way. I don't think we'll be usign
Apache for
>>>>>>>>>> pre-build
>>>>>>>>>> client downloads.
>>>>>>>>>>
>>>>>>>>>> So, I have a question -- who will be setting up the
SF packs
>>>>>>>>>> and will
>>>>>>>>>> they
>>>>>>>>>> just stick with the current structure on that system
for DLs --
>>>>>>>>>>
>>>>>>>>>> i.e.
>>>>>>>>>>
>>>>>>>>>> <root>/files/stable/<version>/
>>>>>>>>>> <pack name>
>>>>>>>>>>
>>>>>>>>>> and
>>>>>>>>>>
>>>>>>>>>> <root>/files/localized/<language>/<version>/<pack
name>
>>>>>>>>>>
>>>>>>>>>> I'm hoping the answer is "YES".
>>>>>>>>>
>>>>>>>>> Whatever we do, let's try to get a directory schem that
works
>>>>>>>>> now and
>>>>>>>>> for AOO 3.4.1 and AOO 3.5 and for AOO 4.0, etc.. �This
is not
>>>>>>>>> something where it will be easier to clean up later.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Honestly spoken, I don't know if this will work.
>>>>>>>>
>>>>>>>> Of course it could be easy and fast to think about a directory
>>>>>>>> structure
>>>>>>>> that will work also for a AOO 5.0 release.
>>>>>>>>
>>>>>>>> However, I doubt that we will have the time to make the DL
logic
>>>>>>>> work this
>>>>>>>> way, too.
>>>>>>>>
>>>>>>>> As I've no idea how close we are from the first public download
of
>>>>>>>> AOO 3.4 I
>>>>>>>> wouldn't do bigger changes now.
>>>>>>>>
>>>>>>>>
>>>>>>>>> Thinking ahead, what do we do when we have a new release,
like a
>>>>>>>>> 3.4.1? �And what can we do now to make that future
less painful?
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The DL logic for 3.4.1 can be the same as for 3.4.0. There
>>>>>>>> shouldn't
>>>>>>>> be big
>>>>>>>> changes. For further releases see above.
>>>>>>>>
>>>>>>>> Juergen is already OK to setup the structure like it was
in the old
>>>>>>>> project,
>>>>>>>> so that the need changes to the DL logic is minimal.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> It seems the easiest way to go to me too.
>>>>>>>
>>>>>>> Roberto
>>>>>>
>>>>>> OK, I need some clarification here -- again.
>>>>>>
>>>>>> I am to understand by the above statements by Marcus and Roberto
that
>>>>>> the directory structure for 3.4 will be the same as it is for 3.3,
>>>>>> but....
>>>>>>
>>>>>>
>>>>>> we will have a *different* structure on www.apache.org/dist? Also,
>>>>>> OK,
>>>>>> we just need some awareness.
>>>>>>
>>>>>> So -- can someone tell me what's what here.
>>>>>
>>>>> I am currently also confused. I would still prefer my proposed
>>>>> structure
>>>>> in the beginning of this thread if it is possible.
>>>>>
>>>>> That would allow us to easy add further platforms and keep the bits a
>>>>> little bit separated. Think about 100 languages and 5 files (including
>>>>> the checksum files) for each downloadable file.
>>>>>
>>>>
>>>>
>>>> Maybe it will look more clean but thats not important. Normally the
>>>> average user should not be pointed to a mirror to find her/his favorite
>>>> file. For this we have the user-friendly and one-click-download
>>>> webpages.
>>>>
>>>> For the former OOo release the structure was very good and also
>>>> scalable
>>>> for new releases and languages. And it is much easier to upload
>>>> everything into a flat structure.
>>>>
>>>>
>>>
>>> I can't really see a flat structure in the old directory tree. One
>>> directory for each language etc.
>>
>> OK, maybe it was not the right wording and my thinking not correct.
>>
>> So, your idea is the following:
>>
>> <root path>/ooo/<version>/source/...
>> <root path>/ooo/<version>/<platform>/...
>> <root path>/ooo/<version>/<platform>/languagepacks/...
>>
>> It seems there is not other ASF project with releases for specific
>> platforms *and* languages (otherwise please point me to the project), so
>> maybe we can stick with this and divide only into platform-specifc
>> directories.
>>
>> Maybe we can agree on the following structure for a AOO 3.5 release?
>>
>> <root path>/dist/incubator/ooo/<version>/src/...
>> <root path>/dist/incubator/ooo/<version>/bin/<platform>/...
>>
>
> why should we add a further indirection "bin" here? Keep it simple!
> Either we split in different platform directories or we can use one for
> all but not both.

Because with your initial path structure proposal I thought you want to 
be more Apache-compliance. Other projects have this setup.

Of course we don't need to copy this. :-)

> We will discuss the future structure in new thread asap to have enough
> time to adapt the scripts.

OK

Marcus

>> If necessary we can provide additional files as subdirs inside the
>> <version>/ directory (e.g., documentation in "docs/", hotfixes in
>> "patches/", etc.).
>>
>> And new releases as Beta or RC can be uploaded into a new and own
>> <version>/ subdirectory.
>>
>> BTW:
>> The checksum files are created for every file and checksum format
>> separately, right? Do we have to store them together with the respective
>> files? Or is it allowed to store them in a separate directory?
>>
>>>> To have every version, platform and
>>>> language in its own directory is much more complicated to handle in the
>>>> DL scripts.
>>>>
>>>>
>>>
>>> My proposed structure used the version as start directory and than
>>> only split the platforms and the language packs but that can be
>>> dropped if it makes things easier. Then we would have a very flat
>>> structure.
>>
>> I would prefer to have them together with the full builds.
>>
>>> I really don't see here a technical problem to put the already
>>> collected items (platform, lang, version, mirror...) in the right
>>> order to prepare a download url.
>>
>> There is indeed no technical problem. It's only a problem to get there
>> in time. ;-)
>>
>>> But anyway we will keep the old structure for now
>>
>> Thanks again. :-)
>>
>> Marcus
>>
>>
>>
>>>> Currently we can assume that all platform files are in the same
>>>> location. You would like to split them up into different this has to be
>>>> taken into account. Plus the lanuages.
>>>>
>>> All languages in the same directory only language packs goes in a sub
>>> directory.
>>>>
>>>>> And it will work for future releases as well.
>>>>>
>>>>> I have agreed to use the same structure as for 3.3 but I also have
>>>>> said
>>>>> that I skip the version in the localized folder because we already
>>>>> have
>>>>> it in the path. No direct feedback on this and I took it as common
>>>>> consensus.
>>>>>
>>>>> But now I am confused. We should clarify the structure before I will
>>>>> start the upload tomorrow.
>>>>>
>>>>
>>>>
>>>> To make it short (and maybe painful ;-) ). When you don't create the
>>>> sam
>>>> edirectory structure than for OOo 3.3.0, then I'm pretty sure the DL
>>>> logic will not work.
>>>>
>>>> For the structure as reference please have a look here:
>>>>
>>>> http://openoffice.mirrorbrain.org/files/stable/3.3.0/
>>>> http://openoffice.mirrorbrain.org/files/localized/de/3.3.0/
>>>>
>>>> So, when you will start the upload tomorrow, I think we are pretty
>>>> close
>>>> to our official release. IMHO too less time to rework the DL logic
>>>> for a
>>>> new structure.
>>>>
>>>>> I haven't looked in the details behind the download scripts and don't
>>>>> know how much work it is to adapt them to a new directory structure.
>>>>> That means I will use the structure that will work for now.
>>>>>
>>>>
>>>>
>>>> Thanks.
>>>>
>>>> I really believe you that you want to improve the structure (e.g., I
>>>> could think of the split into stable and localized, this is IMHO no
>>>> longer needed and could be brought together) but we shouldn't change
>>>> this now.
>>>>
>>>> Marcus
>>>>
>>>>>> I CAN change the friendly scripts to go with the NEW (Apache)
>>>>>> structure.
>>>>>> In fact I'm going to work on THAT approach today (along with Rob's
>>>>>> changes) and hopefully we'll be set for either instance.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>> To setup a new structure that makes maybe more sense can
be done
>>>>>>>> later for a
>>>>>>>> release after 3.4.x.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> my 2 ct
>>>>>>>>
>>>>>>>> Marcus

Mime
View raw message