chei0aiV

46 ms·

481.
by chei0aiV 11y ago
Make it work without JavaScript: https://en.wikipedia.org/wiki/Progressive_enhancement
482.
by chei0aiV 11y ago
Sounds like you might want one of these: http://neo900.org/
483.
History of largest strongly connected component in Debian bootstrap(bootstrap.debian.net)
31 points by chei0aiV 11y ago|15 comments
484.
by chei0aiV 11y ago
What is the killer part of PPAs? It is pretty easy to setup your own repo on a server using reprepro or aptly. Is it the build-machines-as-a-service aspect? Or the ease of adding a PPA to your system? Or the fact anyone can dump some stuff
485.
by chei0aiV 11y ago
I thought this was about antifeatures: http://wiki.mako.cc/Antifeatures
486.
by chei0aiV 11y ago
Some exist already: http://www.harukizaemon.com/simian/ http://dickgrune.com/Programs/similarity_tester/ https://github.com/silviocesare/Clonewise
487.
by chei0aiV 11y ago
Oh. Obviously for internal libraries you should do whatever you like, including bundling. I thought you were talking about open source libraries.
488.
by chei0aiV 11y ago
I think I would prefer to base on proven libraries with stable interfaces. Do you have any examples of these breakages?
489.
by chei0aiV 11y ago
There are some tools to help out with that: https://wiki.debian.org/AutomaticPackagingTools https://summit.debconf.org/debconf15/meeting/257/automatic-p...
490.
Automatic packaging tools in Debian(wiki.debian.org)
4 points by chei0aiV 11y ago|0 comments
491.
by chei0aiV 11y ago
Why do applications want different versions of libraries instead of being portable?
492.
by chei0aiV 11y ago
https://packages.debian.org/prometheus
493.
by chei0aiV 11y ago
To the downvoters: the comments on that post mention a lot of deployment methods that people not doing Debops are using.
494.
by chei0aiV 11y ago
To not bundle dependencies, use the Java packages in Debian stable and if you find one with a missing feature or unfixed bug, then backport that from Debian unstable or from upstream.
495.
Desktop Unix has not arrived(polka.bike)
3 points by chei0aiV 11y ago|1 comments
496.
by chei0aiV 11y ago
They are doing stuff like this: https://news.ycombinator.com/item?id=9952356
497.
Debops (2014)(enricozini.org)
190 points by chei0aiV 11y ago|93 comments
498.
by chei0aiV 11y ago
Personally I would use standard practices of the open source world; package your app properly into a .deb/.rpm, deploy that and push configuration for it out using puppet/ansible/etc. aka, debops! https://enricozin
499.
by chei0aiV 11y ago
The big problem is device support and how vendors approach that. They just throw crappy Linux BSPs over the wall for GPL compliance. For any community project to approach Android levels of device support is impossible because it takes a mul
500.
by chei0aiV 11y ago
Are you working on merging the Linux kernel forks back into the mainline Linux kernel? Will you port to the Neo900 when it comes out?
501.
by chei0aiV 11y ago
There is a real successor to the N900 called Neo900: http://neo900.org/ Still in development but some really cool stuff like isolation of the modem.
502.
by chei0aiV 11y ago
The libav fork of ffmpeg was primarily for technical reasons. Luckily those technical reasons have improved since the fork.
503.
by chei0aiV 11y ago
Don't connect to your servers from machines you don't/shouldn't trust.
504.
by chei0aiV 11y ago
This: When internet adoption began to take off in the 1990s, it came with skeptics and an endless series of questions. In 1995, Newsweek published an article titled “Why the Web Won’t be Nirvana,” stating: “Visionaries see a future of telec
505.
by chei0aiV 11y ago
A few followups: http://ebb.org/bkuhn/blog/2015/07/15/ubuntu-ip-policy.html https://mjg59.dreamwidth.org/35969.html http://jriddell.org/2015/07/15/ubu