zaryob / inary Goto Github PK

The packager gives: package name, package summary, package description, package address build dependencies and action functions. Inary get packager name and email in ~/.packager file, set sha1sum, archive type in archive file, set runtime dependencies in pkgconfig (for c c++ and others), requirements.txt (for python), gemfile (for ruby) and others.
In bump versioning it will only get new release. If problem detected building with new release packager control spec file.

I thing comar script will be yaml type. It look a like travis.yml file. And not used python script in comar script and ı thing it will be understandable with this type

I think scom start with inary

İkon temalarda optipng ile optimize etme fikri getirildi.

Api module will be little functions. Declarate all packages and modules into api.py and set enviroments and globals in api.py. The other functions move a new function. In this way api.py will import faster and inary work faster than old pisi versions

sh ~$ inary ro

Unhandled internal exception.
Please file a bug report to <http://bugs.sulin.org>.
<class 'inary.errors.PrivilegeError'>: You have to be root for this operation.
Please use 'inary help' for general help.

Traceback:
  File "/usr/bin/inary", line 97, in <module>
    cli.run_command()
  File "/usr/lib/python3.7/site-packages/inary/cli/inarycli.py", line 155, in run_command
    self.command.run()
  File "/usr/lib/python3.7/site-packages/inary/cli/removeorphaned.py", line 59, in run
    remove.remove(orphaned)
  File "/usr/lib/python3.7/site-packages/inary/util.py", line 84, in wrapper
    raise inary.errors.PrivilegeError(_("You have to be root for this operation."))

Some look and feel fixes...

1:autogen.sh çalıştırma
2:pip ile lokal dosyadan paket oluşturma
3:cargo ile rust için paket oluşturma
...

When a command or package is writen false, anythşng cannot understands easly. So, we need a decorator like @spell to return did you mean message.

sh ~$ inary up
Updating repositories.
Updating package repository: "core"
No signature found for "/repo/SulinRepository/inary-index.xml"
Package database updated.
Checking dependencies for install...
The following packages will be upgraded:
libsoup  libsoup-devel
Total size of package(s): 0.00  B / 410.70 KB
After this operation, -4160.00  B space will be freed.
Downloading 1 / 2

In this place

After this operation, -4160.00  B space will be freed.

It needs some look and feel fix

Pisi/fetcher.py used urlgrabber module. But urlgrabber not compatible with python3.
We should write new fetcher. There are alternatives for this:
*pycurl
*requests
*httplib and ftplib
*urllib.request

Why we build packages under root user?? Is this logical??

In old TODO.md
-> Refactor code after unit tests are finished. Divide long functions. Rename necessary function and variable names (like A, B_C, D_, C) to understandable ones
-> Add documentation to all module functions
-> Messages in log file are not very helpful. Log messages overhaul needed. We need detailed logging.
-> Create meaningful Exception classes. Remove "Error" exceptions and humanized error messages after Exception work done

when building we use catbox or the other sandboxing modules. I thing it's short. Maybe we can use lxc (linux containers) when package building in future

A detailed documentation is necessary for our package manager.

Pisi not developed since 2011. (After pardus project didn't make big changes on pisi) And pisi name already used and owned from https://github.com/examachine/
I dont want debate with anybody due to a name. Thats' why I will be change pisi and all C Based requirements (piksemel and catbox)

Pisi renamed named Inary

We need simulation mode
print full log without download and install (just print log)

İnary uses old catbox sandbox system but it is really slow. Needs to looking for necessities for new sandbox enviroment or developing catbox enviroment.