Add asn1c/0.9.28

[theirix]

Specify library name and version: asn1c/0.9.28

This is also a good place to share with all of us why you are submitting this PR (specially if it is a new addition to ConanCenter): is it a dependency of other libraries you want to package? Are you the author of the library? Thanks!

---

• I've read the guidelines for contributing.
• I've followed the PEP8 style guides for Python code in the recipes.
• I've used the latest Conan client version.
• I've tried at least one configuration locally with the conan-center hook activated.

[uilianries]

Conan Center Index is moving toward to Conan 2.0

Some linters are checking if new PRs are minimally compatible with Conan 2.0. As some methods will be removed in the future, the linter asks to update them.

[uilianries]

Suggested change

	from conans import ConanFile, AutoToolsBuildEnvironment, tools
	from conans.errors import ConanInvalidConfiguration
	from conan import ConanFile
	from conan.tools.files import get, rmdir, chdir
	from conans import AutoToolsBuildEnvironment, tools
	from conan.errors import ConanInvalidConfiguration

[uilianries]

Suggested change

	required_conan_version = ">=1.33.0"
	required_conan_version = ">=1.47.0"

[uilianries]

Suggested change

	tools.get(**self.conan_data["sources"][self.version],
	get(self, **self.conan_data["sources"][self.version],

[uilianries]

Suggested change

	with tools.chdir(self._source_subfolder):
	with chdir(self, self._source_subfolder):

[uilianries]

Suggested change

	tools.rmdir(os.path.join(self.package_folder, "res", "doc"))
	tools.rmdir(os.path.join(self.package_folder, "res", "man"))
	rmdir(self, os.path.join(self.package_folder, "res", "doc"))
	rmdir(self, os.path.join(self.package_folder, "res", "man"))

[uilianries]

Suggested change

	from conans import ConanFile, CMake, tools
	from conans import CMake
	from conan import ConanFile
	from conan.tools.build import cross_building

[uilianries]

Suggested change

	if not tools.cross_building(self):
	if not cross_building(self):

[theirix]

@uilianries , thanks for suggestions! What a coincidence, I have already prepared almost the same changes :-)

Anyway I was confused by a few problems.

1. How to replace a very popular os_info? I do not see equivalents for tools.os_info and others in conan package.

2. Is it right that for 2.0-ready recipes we have not have any conans imports? Docs stated that. If so, should we place feature requests to the Conan?

3. Conan-center's pylint-based v2 linter is amazing. How can I run it locally?

[uilianries]

@theirix

How to replace a very popular os_info? I do not see equivalents for tools.os_info and others in conan package.

It's still not available (ported). I suggest you opening an issue to Conan client, because they are removing many things and if you explain your case, there is a chance of porting it.

Is it right that for 2.0-ready recipes we have not have any conans imports? Docs stated that. If so, should we place feature requests to the Conan?

True, some of them are being migrated. For instance, check_min_cppstd requires Conan 1.50, which is not running on Conan Center yet. Placing a new feature request to keep tools which you judge as important is the best move, as more people can have same situation.

Conan-center's pylint-based v2 linter is amazing. How can I run it locally?

Excellent question! Indeed, it deserves a documentation. In short term, you need to copy the linter folder locally (which you already have with your git clone to conan-center-index), then you need to run those steps listed on Github Actions: https://github.com/conan-io/conan-center-index/blob/master/.github/workflows/linter-conan-v2.yml#L82. Of course, don't forget to install pylint first.

For instance:

$ pylint --rcfile=linter/pylintrc_recipe recipes/boost/all/conanfile.py

[conan-center-bot]

All green in build 6 (b37c9ab2393d67a6bda38c62757a6cf60532fa73):

• asn1c/0.9.28@:
  All packages built successfully! (All logs)

  🔸 Informative: This recipe is not ready for Conan v2

  _{We have started the migration process to Conan v2 and exporting recipes successfully will be required in the future.
  This is just an informative note to gain awareness about the process, no need to take any action. The plan is to enforce smaller steps that are easier to fix and, eventually, this conan export step will work.
  See the recipe migration guide to know more about the changes required.}

  ERROR: Error loading conanfile at '/home/conan/w/prod_cci_PR-12015/recipes/asn1c/all/conanfile.py': Unable to load conanfile in /home/conan/w/prod_cci_PR-12015/recipes/asn1c/all/conanfile.py
    File "<frozen importlib._bootstrap_external>", line 728, in exec_module
    File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
    File "/home/conan/w/prod_cci_PR-12015/recipes/asn1c/all/conanfile.py", line 1, in <module>
      from conans import AutoToolsBuildEnvironment, tools
  ImportError: cannot import name 'AutoToolsBuildEnvironment' from 'conans' (/opt/pyenv/versions/3.7.13/lib/python3.7/site-packages/conans/__init__.py)