Comments (8)
Unfortunately, there was a freeze policy at that moment. Debian just opened to upload new packages after Debian 12 was released.
Now, I am looking into a warning in the man page [1]. I hope I can upload 1.6.2 or a newer version to Debian when I resolve this issue.
[1] https://gavinlai-guest.pages.debian.net/-/cgreen/-/jobs/4560875/artifacts/debian/output/lintian.html
from cgreen.
Release 1.6.2 published!
I don't know what the plans for the packaging structure is at this point, put I found it to be a bit ... surprising for some old packaging I tried. It probably followed Debian "rules", but as a user of the package I found the partitioning unnatural for a app that is only used by developers.
So if I may, I'd like to request that an installation of cgreen1
includes both the tools, the library and the header files, as all those are required when using Cgreen
. In a manner, there is no "app" package, only the "-dev" package.
Again, that is only my suggestion for making the package easier to install for the "users", which are always "developers".
from cgreen.
After reading your comments, I read the Debian policy again carefully. I think the maintainer separates the files into packages correctly.
However, I know users need the tools, library, and header files in general. Command "apt-get install cgreen1" simply install these things would be easier for the users.
Here's my approach:
Instead of putting tools, the library, and the header files into "cgreen1" package, I think we just need to make sure the command "apt-get install cgreen1" installs the files we expect.
The current situation is cgreen1 depends on libcgreen1, so I don't need to handle this part. It will definitely install libcgreen1 when "apt-get install cgreen1". The only thing I need to handle is the header files. I think the most precise relationship in debian/control is Recommends.
Recommends
This declares a strong, but not absolute, dependency.
The Recommends field should list packages that would be found together with this one in all but unusual installations.
By default, "apt-get install" will also install "Recommends" packages.
I will add "Recommends libcgreen1-dev" into cgreen1. With this, "apt-get install cgreen1" will install the files we expect.
I hope my approach can fit your suggestion.
However, my change still needs to be reviewed by Debian procedure, so I cannot promise anything at this moment. Maybe I miss something.
from cgreen.
Unfortunately, there was a freeze policy at that moment. Debian just opened to upload new packages after Debian 12 was released.
Now, I am looking into a warning in the man page [1]. I hope I can upload 1.6.2 or a newer version to Debian when I resolve this issue.
[1] https://gavinlai-guest.pages.debian.net/-/cgreen/-/jobs/4560875/artifacts/debian/output/lintian.html
I just had a pull request in #322 to fix the lintian. Please have a review. Thanks!
from cgreen.
With just a quick look at the log that might be related to a fix that is done after 1.6.1. Could you just try the same tests with HEAD. If that passes I can release a 1.6.2.
from cgreen.
Thanks for your prompt reply! It passes the test in i386 [1] with the HEAD commit (98c2550).
A release of 1.6.2 will be appreciated : )
[1] https://salsa.debian.org/gavinlai-guest/cgreen/-/pipelines/505623
from cgreen.
Yes, I think that is an approach that will work. Hope it passes Debian scrutiny ;-) Perhaps there is a way to add a comment to the reason for doing so.
from cgreen.
Any update on this? Repology indicates that a few platforms has moved to 1.6.2 but not Debian, and thus not Ubuntu...
from cgreen.
Related Issues (20)
- CMake warning: Could NOT find LibBfd HOT 4
- Never seem to get a cgreen-runner executable HOT 5
- The libbfd dependence issue in Debian HOT 14
- Test helper scripts should use sh instead of bash for maximum portability
- Revert dependency on libbfd HOT 1
- Make learning mocks print immediately HOT 4
- Add documentation on compile time configuration
- create_xml_reporter() crashes on MSYS platform HOT 2
- CUTE reporter final report statistics zero
- CUTE reporter per test time invalid HOT 2
- Option for unbuffered stdout for cgreen-runner HOT 1
- Test signal HOT 1
- [1.6.2] Version marked as 1.6.1 in the Cmake file HOT 1
- "cgreen-runner --quiet" results in "unrecognised option" HOT 3
- "cgreen-runner --verbose" is not HOT 2
- Default text reporter does not show names of failed tests HOT 2
- cannot pass unit test in s390x HOT 31
- offer a mechanism to skip tests at runtime HOT 2
- Use custom reporter with cgreen-runner
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cgreen.