WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: fcitx tcz extension email is received correctly?  (Read 180 times)

Offline Zhe

  • Newbie
  • *
  • Posts: 5
fcitx tcz extension email is received correctly?
« on: September 15, 2025, 10:55:35 AM »
I sent an email titled "fcitx.tcz.tar"   (include  fcitx, fcitx-config-gtk, opencc, clipit, and  aircrack-ng[update]),  attachments are not encrypted with bcrypt, This is my oversight. If there is anything wrong, please correct me. Thank you.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12241
Re: fcitx tcz extension email is received correctly?
« Reply #1 on: September 15, 2025, 11:25:41 AM »
Hi Zhe
Welcome to the forum.

It is considered a good idea to bcrypt submissions so the attachments do not
get flagged as being malicious, as shown here:
https://wiki.tinycorelinux.net/doku.php?id=wiki:creating_extensions#submitting

Offline Zhe

  • Newbie
  • *
  • Posts: 5
Re: fcitx tcz extension email is received correctly?
« Reply #2 on: September 16, 2025, 02:25:21 AM »
I sent the email again.

core_x86_tcz.tar.gz.bfe (14.94M)    include ( fcitx ,fcitx-config-gtk , opencc, clipit ,extra-cmake-modules, aircrack-ng )

PS: why submitqc: opencc.tcz library inclusion disabled on commandline. (other tcz report this also)?

/tmp/submitqc/missingdeps

these tcz can work well on my PC

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15248
Re: fcitx tcz extension email is received correctly?
« Reply #3 on: September 16, 2025, 04:48:48 AM »
I received your bcrypted submission - thanks for your contribution.

As per the wiki extension submission guidelines:

Your build notes/script for each extension should be included so I can check if the correct tinycorelinux build flags have been used.
The binaries and libraries in each extension should be stripped
The extensions should be divided up into extension.tcz, extension-dev.tcz, extension-doc.tcz, extension-locale.tcz, etc
lib*.la files should not be included in any extensions
Prior to submitting an update to an existing extension, you should pm the maintainer to check if they are OK with you submitting an update
The source code tarball and any patches used should be submitted with the extension.

Could you resubmit with the above taken into account.

Offline Zhe

  • Newbie
  • *
  • Posts: 5
Re: fcitx tcz extension email is received correctly?
« Reply #4 on: Today at 02:18:02 AM »
Thank you for your correction.

build notes/script:
I manually downloaded, extracted, and compiled these extensions.
so ...  I can only try to find it from the bash command history (from a month ago). hoping it hasn't been overwritten.
I cannot promise that I will definitely be able to do it.
The compilation dependencies referenced ( https://archlinux.org/packages/extra/x86_64/fcitx/ ), .etc

build flags :
(I added them to the .profile.)
export CFLAGS="-march=i486 -mtune=i686 -Os -pipe -fexceptions"
export CXXFLAGS="-march=i486 -mtune=i686 -Os -pipe -fexceptions"
export LDFLAGS="-Wl,-O1"

./config --prefix=/usr/local  is uesd

source code:
source file can be downloaded via the URL in the tcz.info file.
If there is an error in the compilation process, it is mostly due to missing dependencies,
no specific patch used.

In my spare time, I will do these work:
add build notes (dependencies)
strip debug symbols, remove *.la files
Split extension -> dev.tcz, doc.tcz, locale.tcz
remove aircrack-ng.tcz update

Maybe it will be completed in a few weeks.