frue-project / fpkg Goto Github PK

add dependency resolving using something like libsolv or something

This will have to wait 'till we have a working dependencies system, but once we've done it, we should implement functionality to check every package by name if it's a dependency for others or not.

Ofc, there are still "top-level" packages that aren't a dependency for anything else, but we can think of a way to specifically mark those (in the metadata file maybe).

More universal, don't think I need to say more

I think every archive with a package should contain a simple text file, which describes things like name, version, dependencies, author etc. We just have to agree on a format, i.e. what it will contain.

Also it would be nice if the archive contained a list of where each file / directory should land, i.e. where in the FS it should be copied to.

This is just future-proofing stuff.

Rn we don't have an issues temlate; would be nice to have some

It's nice to have the delays in fpkg and all, but sometimes you just want to get things done quick.

I propose we do it the following way: we crate our own function in place of sleep (call it 'sleepy' or sth), which will check if a command-line variable (say 'fast') is present, and call or not call sleep with the appropriate duration.

We'd create the "download-only" FPKG dir either in ~/Downloads of a user or in /var/, I see no need in creation of a separate /home/FPKG directory

Describe le bug
Currently our code has no cleanup functionality, which is bad. We should def look into this.

When we continue expanding the repos, there's a possibility of two or more repos containing a package with the same name. In that case we should prompt the user which one to install.

It's just that when we search for the package in our local lists, we should take ALL entries, not just the first one, and print them as list if there is more than one.

Bc packages almost always contain more than a single file, would be good to have a place where to keep track of all the files installed by various packages.

For example: we create a dir at /etc/fpkg/; there, we will have configs etc, but also a subdir 'packages'; in this subdir, there will be a directory with the package name, which will hold a file named fileslist or sth, where on each line there will be the full path to the installed files from this package.

I think this will make removal cleaner. Also, the package dir can hold other things like metadata.