In Other BSDs for 2014/05/03

Updated late this week because of circumstances.

In Other BSDs for 2014/04/26

Another active week.

In Other BSDs for 2014/04/19

I’ve got “coverage” of most every BSD this week.

In Other BSDs for 2014/04/05

Another week.

In Other BSDs for 2014/03/22

I have a list of commits I’ve saved between the various BSDs of licenses getting corrected to the 2-clause BSD license; that would definitely be a good cross-BSD project to sync.

In Other BSDs for 2014/03/15

Another week with lots of links.

In Other BSDs for 2014/03/08

Links everywhere this week!

In Other BSDs for 2014/02/22

Read the first item, if nothing else.

 

 

 

In Other BSDs for 2014/02/15

Lots of links, yet again.

In Other BSDs for 2014/02/08

As you read this, I’m at NYCBSDCon – or at least should be.

In Other BSDs for 2014/02/01

For once, I got this mostly done before late Friday night!

In Other BSDs for 2014/01/11

Running late putting this together…  Back to bullets!

In Other BSDs for 2013/12/21

Odds and ends for the quieter holidays.

A BSD plan: license summaries

I had a sometimes-great, sometimes-difficult trip to New York City over the past few days, and while I was there, I met the ball of energy that is George Rosamond of NYCBUG (which is having a huge party right now.)  He and I talked for a bit about various aspects of the BSD ecosystem, and one thing he noted was that people aren’t generally aware of all the licenses in use for the different software packages on the system, or even the individual licenses in the system files.

There is an ACCEPTABLE_LICENSES setting in pkgsrc, where software licensed under terms not in that list won’t install.  That’s useful, but frustrating, because it keeps people from getting what they asked for – a software install.  Something that would be useful – and it could be cross-BSD very easily – would be a license audit summary.

There’s meta-data on every package in FreeBSD’s ports and DragonFly’s dports and pkgsrc and OpenBSD’s port system.  Why not say ‘pkg licenses’ in the same way you can say ‘pkg info’, and get a summary of the licenses you have installed in the system?  (or pkg_licenses, etc.  You get the idea)  This wouldn’t prevent people from installing software, but it would give a very quick view of what you were using.


> pkg licenses

Software package    License
----------------    -------
foo-2.2.26          Apache license
bar-7.999999        Donateware
baz_ware-20131209   MIT
quux-silly-6.5      BSD

It could be extended to the base system, but I’d like to see this in all the packaging systems as a common idea, in the same way that ‘info’ in a packaging command always shows what’s installed.

In Other BSDs for 2013/12/07

Happy birthday to me!

In Other BSDs for 2013/11/16

Not as much pulled directly from the source lists this time, which is good.

 

In Other BSDs for 2013/11/09

Not sure why, but there wasn’t a lot of things this week to pick out.

 

In Other BSDs for 2013/11/02

There’s a surprisingly large list this week.

Discontented with contention? Be content.

Matthew Dillon wrote a roundup post summarizing all the changes he’s made to DragonFly to improve SMP performance in the last few weeks.  He’s removed almost all contention from DragonFly.  This means better performance, scaling upward depending on the number of processors.

‘monster’, the system that builds all 20,000 items in dports, can complete the run in 15 hours.  Compare this to the 2 weeks it used to take me to build the 12,000 packages in pkgsrc.  This is admittedly on different hardware and different packaging systems, but it gives a sense of the scale of the improvement.