Hi Tim, it has been said enough regarding the maintenance of newly added packages.
One thing I'm interested in would be the theory of making a "distribution". As you said you have a distro, I'd be interested in how you manage dependencies. Required dependencies are simple, but how do you handle recommended/optionals? What about the difference between runtime- and build-dependencies (that is for example cmake required for building, but not for runtime). And how to handle circular depedencies? Even the package management may not be full featured in automatically install all required pkgs, it is required to have them on the building machine -- Thomas Am Samstag, den 18.07.2015, 21:31 +0200 schrieb Tim Tassonis: > Hi all > > As I'm steadily completing my lfs/blfs based distribution, I've come > across a few packages that are neither in lfs/blfs, but i my opinion > generally useful. > > My question is: Is there any demand for more packages in blfs, or is the > current set more or less what's indended? > > The packages I have built on top and in spirit of blfs and would view as > possible additions are: > > - volumeicon: A nice systray volume control for also, using alsamixer as > mixer and else only depending on gtk. Actively maintained. > - openvpn: SSL VPN client/server solution based on openssl and lzo > - rdesktop: rdp client to connect to windows desktops > > I'd be willing to provide the descriptions in BLFS style, if there is a > demand for that. > > > Cheers > Tim > > -- > decentral.ch - IT Stuff > Tim Tassonis > Dennlerstasse 36 > 8047 Zürich > > [email protected] > +41 79 229 36 17 -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
