On Sun, Dec 06, 2015 at 11:27:51AM +0100, Slávek Banko wrote:
> Yes, that's right - tde-construct is outdated and unmaintained. It is not 
> suitable for use. To create packages for various distributions files are to 
> found in the tde-packaging GIT repository.

That's certainly a hint, but a problem with GITs is usually that
you find what you want/need only if you the GIT already. They're
not overly verbose, and looking at its front page, it's hard to
find information what else is in the branch called "master",
when the only comment about it is the latest commit message.

You who are always working with and on the GIT, will probably know
what is what --- I don't.

A more speaking example: the r14.0.x branch... what is it supposed
to cover? 14.0.1 and 14.0.2? And where has the deprecated dependency
been removed? All (sub)versions or the latest?

Don't misunderstand, I don't expect answers to these questions, as
this is not my current concern; I'm just saying, it's not easy to
find what I need.

Same with the tags section: what are these *.zip and *.tar.gz files
about? Are those the whole sources? Or just utility scripts? Or
maybe even meta data used for packaging? GIT is noncomittal in this
respect, too, in that it doesn't tell the file sizes, so I could
try my talent for educated guesses ;-)

wget -S only tells me "Length: unspecified [application/x-gzip]",
so no help via classic http, too. And I don't currently have the
bandwidth to simply download everything (my *core.tar download,
which is stable from the sweden mirror, is still at 45% after 5h ;-).

Also the "tree" tab doesn't reveal much to me. My actual target,
slackware, is empty except a .gitignore file, but also looking at
others, like suse, I continue lacking any idea about what the files
might be for (I've seen a lot of *.diff files, but diffs for what?)
(Again: purely rhetorical questions) 

Some more info in pure HTML format would be appreciated, and I guess
not only from my side, but that's not the actual point of this post.

Anyway, I'll try to find my way in the hope that the ambiguities
regarding the build methods (which were those? iirc, cmake and
autoconf? --- Well, I'll see) have been removed meanwhile.

Best regards, and still thanks ;-)
Jagged

-- 
valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error