New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Towards a packaged distribution of the RASCSI software #740
Comments
Great suggestions! As I get more time, I'll mentally digest this as I get more time. Regarding the .deb packages - I've been thinking of going more the embedded route (potentially a buildroot image). There are pros and cons to both, I suppose. |
with "embedded route", you mean distributing disk images for SD cards. do you? this seems not too ergonomic for software updates to me. i'm certainly interested in a pro/con-list for that matter. |
One of the biggest complaints I get about RaSCSI is the boot up time. Using off-the-shelf Linux distros doesn't help with this. With a pre-made image I can do things to speed up boot time. I'm curious if most users have the Raspberry Pi dedicated to the RaSCSI function, or if they're running other things on there. Ultimately, both are good methods to distribute the software. |
I don't intend to use my RaSCSI Raspberry Pi for anything other than RaSCSI related purposes, but I do hope to use the extended facilities of Linux to enhance my RaSCSI experience. Example: bridge the Daynaport NIC into a L2 VPN so that I can play AppleTalk network games over the Internet. Needs support for the TAP device, might make use of ebtables, and might upgrade the version of Tinc VPN from what is available in standard repository. |
See #1173 for some discussion on the potential install location for piscsi files. |
initiated from a discussion about proper installtion paths,
i tried to get an understanding of the possibilities and challenges regarding
the distribution of the RASCSI software as Debian packages.
the motivations for that are:
considered
i found one aspect to be a major concern, that is the dependency on other
software that is also not (yet) available as Debian packages, namely:
i can think of three strategies to deal with this:
packages themself
components from source
what also should be figured out is how an
apt
repository could be provided todistribute the resulting RASCSI packages. i haven't done any research on that.
the other aspects and tasks that i found necessary are included in the draft
for a roadmap.
Roadmap
should be located within
/etc
(so that a user that runs a standalone deployment just needs to handle one
set of configurations.)
setuptools
) or one per componenteasyinstall.sh
to seperatescripts
.deb
(source and binary)rascsi
as meta-package that depends these:rascsi-daemon
rascsi-python-tools
orrascsi-{oled,pylib,web}
rascsi-docs
would be optional and include all docs incl. hardwaresoftware
easyinstall.sh
with hints to replacing modes of use or justdrop it?
please let me know when i should be more elaborate to clarify things. or amend
/ correct things, any feedback is appreciated.
regarding myself, i'm not even a RASCSI user yet and i don't have the time to
coninuously participate in another project. but i could certainly help with
progressing the Python parts and the actual packaging.
The text was updated successfully, but these errors were encountered: