kicad-developers team mailing list archive

["Steven A. Falco" <stevenfalco@xxxxxxxxx>]

On 06/02/2018 01:29 AM, Carsten Schoenert wrote:
> Am 02.06.2018 um 02:46 schrieb Steven A. Falco:
>> Wayne - I downloaded the kicad-5.0.0-rc2.tar.xz file you set up.
>> Unfortunately it looks like it was created from inside the
>> kicad-5.0.0-rc2 directory - there is no top level directory:>
>> $ tar tvf kicad-5.0.0-rc2.tar.xz | head
>> -rw-rw-r-- root/root      1739 2018-05-20 21:20 .gitignore
>> drwxrwxr-x root/root         0 2018-05-20 21:20 3d-viewer/
>> drwxrwxr-x root/root         0 2018-05-20 21:20 3d-viewer/3d_cache/
>>
>> In contrast, the kicad-4.0.7.tar.xz file has a top level kicad-4.0.7
>> directory:>
>> saf$ tar tvf kicad-4.0.7.tar.xz | head
>> drwxr-xr-x wstambaugh/Domain Users 0 2017-08-28 10:31 kicad-4.0.7/
>> -rw-r--r-- wstambaugh/Domain Users 1277 2017-08-28 10:31 kicad-4.0.7/.bzrignore
>> -rw-r--r-- wstambaugh/Domain Users   32 2017-08-28 10:31 kicad-4.0.7/.gitconfig
>> drwxr-xr-x wstambaugh/Domain Users    0 2017-08-28 10:31 kicad-4.0.7/3d-viewer/
>>
>> For now I can work around this by rolling my own tar via git-archive,
>> but I think it would be preferable if the 5.x tars followed the 4.0.7
>> structure and had a top level directory.
> 
> That's one more reason for me to not only rely on a upstream tarballs
> that are not generated by an automatic and equal way, they created at
> all from the same source and that is a git tree so I can happily create
> tarballs by myself.
> I guess the KiCad project has simply not enough sources to do a static
> workflow for release with all the needed QS steps. So prefer a released
> version without waiting to long on various related things. It's no shame
> to release a bugfix afterwards if needed.
> 
> The reason for not avvailable tagged releases of kicad-{doc,i18n} is
> simply that contributors should have a realistic time window to get
> recently made changes into their languages.
> I just used the current states to create the needed tarballs as we are
> talking about "just" a release candidate and I also need to look at my
> timetable to get all things together, build, do some tests and upload
> all to the archive on Debian.

Thank you for your perspective.  That helps me understand the process and constraints.

	Steve