hello,
can we resubmit our slackbuilds for 13.1? it's out! Should we use .txz
as extension or $PKGTYPE variable as earlier?
Best regards
Eugene.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner belka...@gmail.com wrote:
Should we use .txz as extension or $PKGTYPE variable as earlier?
I think we should still use $PKGTYPE, but the question is whether the
default should be .txz.
Personally, I'm in favor of changing the default to txz.
hi,
i tested and verified the slackbuilds i maintain for 13.1, they can
just be copied over (less hassle for me :-)
libraries/dietlibc
network/vidalia
as just mentioned already on this list, i as well intend to switch to
the default .txz pkgtype with the next update of those scripts.
--
left
On Tue, May 25, 2010 at 11:03:47AM -0400, Ben Mendis wrote:
On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner
belka...@gmail.com wrote:
Should we use .txz as extension or $PKGTYPE variable as earlier?
I think we should still use $PKGTYPE, but the question is whether
the default should be
For the sake of debate, only. (Please don't take offense at any of my
comments.)
On Tue, May 25, 2010 at 2:29 PM, Rob McGee r...@slackbuilds.org wrote:
xz is a fine tool, possibly superior to gz in every way. But it has
not been around as long.
Linux is a fine tool, possibly superior to
Le Tue, 25 May 2010 13:29:05 -0500,
Rob McGee r...@slackbuilds.org a écrit :
On Tue, May 25, 2010 at 11:03:47AM -0400, Ben Mendis wrote:
On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner
belka...@gmail.com wrote:
Should we use .txz as extension or $PKGTYPE variable as earlier?
I
On 26.05.2010 00:29, Rob McGee wrote:
On Tue, May 25, 2010 at 11:03:47AM -0400, Ben Mendis wrote:
On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner
belka...@gmail.com wrote:
Should we use .txz as extension or $PKGTYPE variable as earlier?
I think we should still use
all the question is about to make the 13.x repo to be retrocompatible or not.
just leave it .tgz,
http://darkstar.ist.utl.pt/slackware/slackware-current/source/a/pkgtools/scripts/
makepkg script adds also .tbz and .tlz as compression options, so if
it's so important to support the new format,
I just flipped a coin, and it came up tails for tgz, so thats my vote.
I flipped a coin because really its a meaningless point considering
one can override the default at build time.
On Wed, May 26, 2010 at 4:11 AM, Leonardo sombr...@gmail.com wrote:
all the question is about to make the 13.x
we decided to use .tgz at least for 13.0
http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-July/004281.html
but now we have 13.1 and I don't think, that there are so many
changes, that sbo couldn't make one more update. We can use standard
slackware format (.txz) and leave it in
On Wed, 26 May 2010 03:12:06 +0100
Eugen Wissner belka...@gmail.com wrote:
we decided to use .tgz at least for 13.0
http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-July/004281.html
As it turned out, we *did* make it configurable by passing an
alternate value to PKGTYPE when
On 05/25/2010 10:30 PM, Robby Workman wrote:
Anyway, since there seems to be some desire for a definitive
statement on this, I'm going to make one:
There are no plans to change the default package compression at
any point in the near future. The reasons include, but are not
necessarily limited
I know there's a bit of anticipation by now, and probably some
pondering as to why we haven't got a set of scripts out there
for 13.1 yet, so I guess some explanation/discussion is in
order...
Basically, the Slackware 13.1 release snuck up on us (yes, even
though several of the SBo admin team
13 matches
Mail list logo
