From owner-freebsd-current@freebsd.org Wed Apr 20 09:48:05 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A02AEB14C48 for ; Wed, 20 Apr 2016 09:48:05 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5BC14173C; Wed, 20 Apr 2016 09:48:05 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1asoju-000ACk-98; Wed, 20 Apr 2016 12:48:06 +0300 Date: Wed, 20 Apr 2016 12:48:06 +0300 From: Slawa Olhovchenkov To: Dan Partelly Cc: David Chisnall , Julian Elischer , Nathan Whitehorn , freebsd-current@freebsd.org Subject: Re: [CFT] packaging the base system with pkg(8) Message-ID: <20160420094806.GJ6614@zxy.spb.ru> References: <76093.1461096570@critter.freebsd.dk> <5716AD65.8070007@shrew.net> <5716FA70.4080604@freebsd.org> <57170E5D.1090701@freebsd.org> <5524F499-5042-407E-9180-43D15A53F3F0@FreeBSD.org> <7621BDAB-A409-456A-A3F1-A6CD9B371DBC@rdsor.ro> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7621BDAB-A409-456A-A3F1-A6CD9B371DBC@rdsor.ro> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 09:48:05 -0000 On Wed, Apr 20, 2016 at 12:00:36PM +0300, Dan Partelly wrote: > IMO, the number of packages per-se is not a problem as long as you > can manage them without arcane commands, aliases, pipe - filters, > or scripts. (they all have their place, but less , the better) My > point is that I don't really want to keep on my head a Unix hacker > hat. I (and presumably many other humans ) like simple things,which > allow me to type a short command (preferably the whole system should > be simple enough to be explained in one-two pages in handbook) , > wait for completion, and get on with my life. Yes and no. While number of packages don't see outside internal -- this is irrelevant. After possibility of update individual package -- nuber of packages is impotant. Take fresh 11.0. Before 11.1 update only kernel. What you system have? 11.0? 11.1-RC3? How you name it? How identify it for take support on forum or mail list? How name system, updated all w/o compiler? or only some services? Currently we have simple naming: 10.3-RC1, 10.3-RELEASE, 10.3-p7, 10.3-STABLE r123456. This is shortly and clearly identify system to anyone. How do this with many packages? I am describe in -pkgbase expirence of updating system. How I am can naming this (my) system? Solaris don't ship new version often and don't have rollover updates. I think, first step may be split to only two package (kernel and world) and resolve many other issuses: distinc base packages from port packages, beadm compatibility, /etc and config updates (/etc/rc.d is not config but currently allowed to editing, this is distinct from plain ports configs) and others. After expirence with this next step will be more clear. > When I said people should pay more attention to Redmond and Cupertino, this is what I meant. UIs are important. Easy service management, fault reporting and so on should be automated. We shouldn't waste our time doing what the computer should do in the first place. Most people want to get the job done, so they can proceed with what is important for them. I am very sorry if this is so offensive to some people that they feel attacked, but unfortunately there aint much I can do to alleviate this. > > > > > 1) The number of packages that the base system has. > > 2) The user interface by which the packages are presented. > > > > I believe (and, please, correct me if I’m wrong), that all of the complaints in this thread have been about the UI, not about the underlying mechanism. That’s not to say that they’re unimportant (quite the reverse), but that they can be solved concurrently with the task of preparing the base system for distribution in packaged form. > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"