Comments (9)
Suggested resolution: ship a list of files and dirs that are going to be created with every fpkg file and it would serve as install and delete list
Suggestion: split created files into categories, that way stuff like configs won't be deleted because of accidental removal
from fpkg.
So sth like (on a single line):
FILENAME/DIRNAME IN TAR:PATH ON FILESYSTEM:TYPE
Assuming ':' is the delimeter.
from fpkg.
I meant rather this kind of file:
files: {
file 1 (/home/${usr}/file1;
file 2 (/usr/bin/file2);
}
And with this categories I meant:
necessary {
file1
}
config {
file2
}
misc {
file3
}
from fpkg.
Shell scripts work much easier with data on a single line, rather than JSON-style data.
We should settle on a file list format before going any further imo.
I propose the following:
There will be 2 lists of files - one for config files (not gonna be deleted in uninstall unless forced to) and one for regular files
They will reside in the tar, and will be copied to the package's folder in '/etc/fpkg/packages'
I propose that in the .tar they be named however the package maintainer likes, and the filenames will be given in the metadata
But once we copy them over, we'll rename them to sth standard like "configs_list" and "files_list"
Each like of the file will be as follows:
PATH_IN_TARBALL:PATH_ON_FILESYSTEM
Ez pz
from fpkg.
I'd propose this layout:
| tar
|-- auto_install_script //if necessary for e.g. config
|-- individual_files
|---- //stuff that goes e.g into ~/.config
|-- program_files
|---- binaries
|---- misc // e.g. license
We'd enforce strict packaging practices in terms of naming of dirs and essential files
from fpkg.
How do you imagine that working with real filenames? I just can't comprehend what's a filename and what's a category description
from fpkg.
Just like C programs have stuff like MAKEFILE or LICENSE that's just always there, we'd also have some fixed names (My example was rather provisional)
from fpkg.
Aha so these are the fixed names you propose
from fpkg.
Not necessarily, we'll discuss the names after we'll set the way of creating of fpkgs
from fpkg.
Related Issues (11)
- Create issues template HOT 1
- Add "fast mode" to fpkg HOT 1
- Package metadata HOT 5
- Use 'wget' instead of 'git' HOT 2
- Create a PKG cache dir during fpkg installation + /tmp/ subdir for downloading files (like /tmp/fpkg-cache) HOT 1
- Add "purge unused packages" option
- Change the described behavior of -d option HOT 1
- Handle packages with the same names HOT 3
- Add cleanup code HOT 4
- dependency resolving
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 fpkg.