dilos-pack-tqt3 #22
Manually merged
TDE
merged 1 commits from dilos-pack-tqt3 into master 5 years ago
No reviewers
No Label
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TDE/tde-packaging#22
Loading…
Reference in new issue
There is no content yet.
Delete Branch 'dilos-pack-tqt3'
Deleting a branch is permanent. It CANNOT be undone. Continue?
try to create a package for DilOS platform
Please,
BASEDIRis a variable used specifically for DilOS?I would expect to use it for example to choose whether to install to
/usror to/opt/trinity– basically to determine the prefix. But I do not understand usingBASEDIRto create a parallel tree? Please, can you explain it to me?just a test...
illumos based systems use BE (boot environment) to upgrade the system.
BE is another location of the system (alternative root)
we modified apt, dpkg and some other tools for this purpose,
i.e. BASEDIR, it is a platform specific issue.
about BEs:
https://docs.oracle.com/cd/E23824_01/html/E21801/index.html
Great, thank you, that's what I needed. Now I understand the meaning of this variable.
One more question: Did you consider that the
dilos-g++directory could be added to the source tree of TQt3?of course, add it in the main tree
Great. In that case you can create a PR to add DilOS mkspec to TDE/tqt3. I assume that after its merging it will be possible to modify this PR to use the files contained in TQt3 instead of the files contained here?
What is the status of this PR, given the new mkspecs files for tqt3 have been merged?
Signed-off-by should be added here for each commit. Since @denis has agreed to DCO, we could possibly add his signature.
please check it and sorry for the delay
There are some shortcomings. First, the Signed-off-by should be on every commit. Second, there is an unnecessary merge commit. But don't worry about it – either I or Michele will fix it for this PR. Over time you will gain further experience with git.
Thank you, guys. I hope my next commits will be correct
After comparing Debian × DilOS packages, I have an additional question – see comments below.
before you send a bugreport.Package: libtqt3-headersArchitecture: anyFor Debian packages, this package is now "all", so it is the same for all architectures. For DilOS, the intent is that the package is "any", so built for each architecture?
at this moment we have two architectures: x86_64 and sparc,
if I specify here "all", sparc failed because some headers placed into a wrong path,
for example, amd64, but it finds in sparcv9 directory
This is strange because both the libtqt3-headers and libtqt3-compat-headers packages contain no architecture-dependent files, and they are all usually installed in a general directory – for example,
/usr/include/tqt3.What files are installed in your architecture-specific directory in your package?
ok, you are right, I just install this packages on sparc, there are no platform specific files
So there seems to be nothing to prevent "any" from being changed to "all" for these packages. Therefore, I modified the commit in this way.
of course, I hope this change will not affect the sparc build
have to install this package.Package: libtqt3-compat-headersArchitecture: anyFor Debian packages, this package is now "all", so it is the same for all architectures. For DilOS, the intent is that the package is "any", so built for each architecture?
20127da5fe.