I don't think it would matter for a PPA in that case. The package manager accepted it without any complaining.Īre there problems with statically linked libraries with the package manager or PPA's? Does Launchpad's build service complain? Or is it just Debian's policy to only accept dynamically linked libraries? Just setting a version, defining the dependencies, a little this and that and then.
#YACREADER UBUNTU INSTALL#
deb package out of some binaries, because I didn't want to install them without the package manager knowing about them. I think I even have a SSH key for it somewhere in my keyring.Ī long long time ago, I created a. I do have a Launchpad account and have signed the Ubuntu Code of Conduct. 1 or 2 weeks ago I would've actually been bored enough to look into it. You can even use my source packages, so you won't have to go through the trouble of creating them from scratch. If you'd like to have a go at creating a launchpad for YACReader yourself I'm happy to help you out. Luis is doing most of the stuff and I help out where I can. YACReader is a project with very little manpower. deb based distro compiling and shipping even these packages is always a bit complicated and time-consuming, which is one of the reasons the newest versions of YACReader are always deployed last for. deb packages which work nicely for most people, but these aren't included in any distro I know of.Īs most of the packaging work for Linux is done by me and I don't even run a. We pursued inclusion into Debian a few months ago, but the project currently is on hiatus due to a pecularity of YACReader needing bits of sourcecode of another software (p7zip) to properly interface it's compression backend (p7zip). Debian and it's derivates have a rather sophisticated packaging system and a lot of rules/practices you have to follow in order to get a proper package. Deploying software on a Debian based platform is not a fun experience.
0 kommentar(er)
