Search Criteria
Package Details: comcom32 0.0.alpha.3.r282.g2147a36-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/comcom32.git (read-only, click to copy) |
---|---|
Package Base: | comcom32 |
Description: | 64 bit command interpreter for fdpp and dosemu2 (comcom64) |
Upstream URL: | https://github.com/dosemu2/comcom64 |
Licenses: | GPL-3.0-or-later |
Conflicts: | comcom32, comcom64 |
Provides: | comcom32, comcom64 |
Submitter: | severach |
Maintainer: | severach |
Last Packager: | severach |
Votes: | 1 |
Popularity: | 0.008708 |
First Submitted: | 2020-04-07 22:22 (UTC) |
Last Updated: | 2024-04-23 15:39 (UTC) |
Dependencies (4)
- dj64 (dj64-gitAUR) (make)
- djstub (djstub-gitAUR) (make)
- git (git-gitAUR) (make)
- thunk_gen (thunk_gen-gitAUR) (make)
Latest Comments
1 2 Next › Last »
severach commented on 2024-03-25 22:15 (UTC)
Conflicting with
djgpp-djcrx-bootstrap
forces people to build djgpp-djcrx and not just run with bootstrap forever. Aborting in prepare doesn't work well. Clean Chroot programs output build() errors but not prepare() errors. This won't matter soon since djgpp utils is going away for dj64dev.We're a long ways off from building comcom-git. I did the first step building smallerc. I added you as a maintainer in case you need to fix stuff building the next packages: stsp/lfanew stsp/djstub stsp/dj64dev and probably more.
dreieck commented on 2024-03-25 20:51 (UTC) (edited on 2024-03-25 21:36 (UTC) by dreieck)
At which point does this conflict with
djgpp-djcrx-bootstrap
?Or is this a "make conflict"?
Then you should not list it in the
conflicts
array but do a test inprepare()
. (Package build is carried out without conflict tests, and built packages do not need to have a working compilation environment.)(I am currently making a ↗ 
comcom-git
$pkgbase
(which should build bothcomcom32-git
andcomcom64-git
), and I stumbled upon this strangeconflicts
entry in yourPKGBUILD
. I did implement such a test inprepare()
-- you can check ↗ here.)Regards!
dreieck commented on 2024-03-25 20:29 (UTC)
Regarding this I have created an ↗ upstream issue.
severach commented on 2024-03-25 19:33 (UTC)
No need as this doesn't build anything new and the -git doesn't compile yet. comcom32 is gone so isn't needed in any form. Delete and make new packages for comcom64.
dreieck commented on 2024-03-25 19:21 (UTC)
Don't forget to increment
$pkgrel
when you update thePKGBUILD
without updating$pkgver
(and then re-generate.SRCINFO
and also add it to the git upload).Seems you have just updated the
PKGBUILD
without a$pkgrel
increment.severach commented on 2024-03-25 18:47 (UTC) (edited on 2024-03-25 18:57 (UTC) by severach)
This is already a git package. Uncomment the -git line in the PKGBUILD. Unfortunately the -git version requires dj64-gcc which I can't find.
dreieck commented on 2024-03-25 18:39 (UTC)
Source checksum verification fails:
… maybe it is time to make a
comcom32-git
andcomcom64-git
anyway, since the latest release is quite old?Regards!
dreieck commented on 2024-03-24 20:27 (UTC) (edited on 2024-03-24 20:28 (UTC) by dreieck)
↗ Here the upstream maintainer of
thunk_gen
, which is a dependency offdpp
, suggests that thecomcom32
-dependency should be moved fromfdpp
(-git
) todosemu2-git
.I forward this suggestion to you so you can check what is the correct way to go.
Regards!
yusuke commented on 2021-07-13 09:44 (UTC)
I couldn't build djgpp-gcc. It gives me compilation errors. I tried both: with yay and without it. I installed first the djgpp-djcrx-bootstrap as are saying here. I get this error:
severach commented on 2021-02-03 20:27 (UTC)
Sounds like you're building djgpp with an AUR helper like yay and it doesn't know there's a last step because it has resolved all the dependencies. The conflicts is there to say that one more step is needed. yay djgpp-gcc should build the first 3 and yay djgpp-djcrx should build the last one. Then yay comcom32 should work.
1 2 Next › Last »