|
Other BSD and UNIX/UNIX-like Any other flavour of BSD or UNIX that does not have a section of its own. |
|
Thread Tools | Display Modes |
|
||||
If it's not broke, don't fix it.
__________________
My Journal Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''. |
|
||||
I really like Slackware, but the package management really doesn't do much for me. Slackware as a whole aims for simplicity, and while the design does reflect this, the developers could easily implement a package management system similar to BSD Ports by using Slackbuilds. After all, Slackbuilds are used by developers to create packages and test them before including them in a release. I particularly like Slackbuilds, since you can specify optimizations in the actual script. Also, syncing isn't necessary either because you can just specify version and reexectue the script, which will result in a package of the newer version. I think it'd be the perfect system. I also think Slackware should move the base of the system to a rolling release system, much like FreeBSD, and allow users to sync and update their systems.
__________________
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." MacBook Pro (Darwin 9), iMac (Darwin 9), iPod Touch (Darwin 9), Dell Optiplex GX620 (FreeBSD 7.1-STABLE) |
|
|||
Hello,
Quote:
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
||||
I don't know how effective that would be. I mean Slackware started in 1993, and it's used the same development model for years. I suppose it's worth a shot.
__________________
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." MacBook Pro (Darwin 9), iMac (Darwin 9), iPod Touch (Darwin 9), Dell Optiplex GX620 (FreeBSD 7.1-STABLE) |
|
|||
Hello,
The worst he can say is no, and you'll be no worse off than you are now.
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
||||
That's definitely true. I'll send him an e-mail tomorrow.
__________________
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." MacBook Pro (Darwin 9), iMac (Darwin 9), iPod Touch (Darwin 9), Dell Optiplex GX620 (FreeBSD 7.1-STABLE) |
|
||||
>That's definitely true. I'll send him an e-mail tomorrow.
If you're using Slack since the early beginning you should already now Pats point of view. A rolling release isn't anything he considers stable and 99.9% of the Slack-Users are quiet happy with the package management. And if you want to show some respect then you shouldn't ask the question some people did ask him again and again. By the way, he has got the famous last word, but he works with a team since years! So if you don't like it, don't use it. I'm using it since the nineties because of this system.
__________________
use UNIX or die :-) |
|
||||
You misunderstood what I said. Slackware doesn't have to change it's development ideology or anything. On the SlackBuilds and Slackware websites, it's noted that the developers use SlackBuilds to build packages and test them before inclusion in a stable release. With that in mind, I think there are two things that could be done.
1. A Ports-style directory containing all the Slackbuilds for a stable release and the patches and whatnot. You install the base system and use SlackBuilds to generate packages and install them. It works better for those of us who don't want to download six CDs or an entire DVD. 2. Have the standard installation available, but include the SlackBuilds directory as an optional item during installaion for those who want to use it. Note, I'm not asking for automatic dependency resolution. SlackBuilds come with dependency information, and the way Slackware and SlackBuilds are developed, you generally don't encounter problems with dependencies. I only need the dependency information so I know what packages to install. I can do everything else manually. Also, if you have a SlackBuilds directory, then everytime a new release is made available, I guess you'd be able to sync your SlackBuilds directory and upgrade all your packages that way.
__________________
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." MacBook Pro (Darwin 9), iMac (Darwin 9), iPod Touch (Darwin 9), Dell Optiplex GX620 (FreeBSD 7.1-STABLE) |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Debian 5.0 released | ephemera | Other BSD and UNIX/UNIX-like | 36 | 26th November 2010 04:50 PM |
NetBSD 5.0 Released! | Android1 | NetBSD General | 8 | 30th April 2009 09:49 PM |
DragonFly BSD 2.2.1 Released! | Android1 | Other BSD and UNIX/UNIX-like | 0 | 30th April 2009 12:51 PM |
DragonFly BSD 2.2 released | matthias | Other BSD and UNIX/UNIX-like | 0 | 18th February 2009 02:37 PM |
NetBSD 4.0.1 Released | JMJ_coder | NetBSD General | 1 | 29th October 2008 03:47 PM |