I am currently in the process of planning a project named strop. In case
you couldn't guess it's going to mimic the ports tree from the various
BSD's of the world.

I am starting to put together the tree now and would like to start coding
this weekend. However I don't want this to all be in vain.

Please reply with why you would like this project or why you wouldn't.
There is a better description at sourceforge. go to sourceforge.net and
search for strop and take a look at the description.

Let me know what all you would like to see improved with the ports trees
of the BSD's and/or if you would find something like this useful.

-link

link wrote:

> I am currently in the process of planning a project named strop. In case
> you couldn't guess it's going to mimic the ports tree from the various
> BSD's of the world.
>
> I am starting to put together the tree now and would like to start coding
> this weekend. However I don't want this to all be in vain.
>
> Please reply with why you would like this project or why you wouldn't.
> There is a better description at sourceforge. go to sourceforge.net and
> search for strop and take a look at the description.

I would like this project if, and only if, we stay with slackware's system
of .SlackBuild scripts. I prefer things the way Pat wanted them, since his
ideas work more often then mine and others who have already tried (i.e.
linuxpackages, slapt-get, swaret, etc). Even then, what good would this
ports system be if we're building from source, since slackware-current
usually already has the most current of everything?

> Let me know what all you would like to see improved with the ports trees
> of the BSD's and/or if you would find something like this useful.
>
> -link

--
"He was a modest, good-humored boy. It was Oxford that made him
insufferable."

link wrote:

> I am currently in the process of planning a project named strop. In
> case you couldn't guess it's going to mimic the ports tree from the
> various BSD's of the world.
>
> I am starting to put together the tree now and would like to start
> coding
> this weekend. However I don't want this to all be in vain.
>
> Please reply with why you would like this project or why you wouldn't.
> There is a better description at sourceforge. go to sourceforge.net
> and search for strop and take a look at the description.
>
> Let me know what all you would like to see improved with the ports
> trees of the BSD's and/or if you would find something like this
> useful.
>
> -link

I think it's great. Somewhere I read that someone else was starting a
similar project... maybe it was linuxpackages.net, hey, maybe it was
you. Check into it and work with whoever is working on it. No sense
having multiple sites.

1. The FreeBSD ports system works great and easy to use. No improvements
needed.
2. Contact P.V. Not to steal your thunder, but Slackware is a, well.. a
picky bunch. Don't get me wrong, good idea, just approach it right.
3. Work with P.V. and to work out a dependency method.
4. Get in included with Slackware and part of his site or it will not be
used (much). Otherwise it would probably be in vain.
5. It would be very useful! Ports are great and the next best is
Slackware's package method.

Use the same cvsup and port commands so I want have to learn anything
else. thanks.
--
Robert - slackware

On Wed, 08 Sep 2004 17:26:51 -0400,
link <link@voidmain.net> wrote:
> strop. In case
> you couldn't guess it's going to mimic the ports tree from the various
> BSD's of the world.

Have fun. You might find <http://slackports.sf.net> useful for ideas.
(The project's now dead.)

--
Mark Hill
Email (Just for Fun):
echo zbp.yvnzt.yyvuez | rot13 | rev | sed s@\\.@\\@@

NeoSadist wrote:
>
> I would like this project if, and only if, we stay with slackware's
> system
> of .SlackBuild scripts. I prefer things the way Pat wanted them,
> since his ideas work more often then mine and others who have already
> tried (i.e.
> linuxpackages, slapt-get, swaret, etc). Even then, what good would
> this ports system be if we're building from source, since
> slackware-current usually already has the most current of everything?

I can see it that this would be setup to install pre-built packages or
build from source like BSD. You could then tailor it to your architect
like 32/64bit when that becomes a issue.

--
Robert - slackware

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, link dared to utter,
> I am currently in the process of planning a project named strop. In case
> you couldn't guess it's going to mimic the ports tree from the various
> BSD's of the world.

I think you've got an uphill battle here. Other people have done
something similar and it's just not really caught on. My personal
feeling is that right now, this is Gentoo's domain, and there's only
room for one ports-like linux distro.

Personally I wouldn't use it. I don't like BSD ports much for a variety
of reasons.

1) Many of the ports don't work. They are either un-maintained or
crippled on certain hardware, meaning you've sorta told some one that
something will work and then it doesn't. There's no gaurantee that the
package will do what I want it to do, and too often they are put
together by people who are only doing it for one system, theirs.
2) General cluelessness. One thing I like about Slackware is it leaves
package management to me, and something like strop just completely
blows that out of the water. I don't trust random joe noob to build the
packages I use on my system. If it doesn't come from me, Pat, or the
people that actually write the software, I don't much trust it.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBP6sklKR45I6cfKARAib6AKCMkHswxgs3xhQbkbDw64 nypkWixgCcCN/m
pB6TKp5QWpIGmFGLE8we5Gk=
=n5L4
-----END PGP SIGNATURE-----

NOTE: This message was sent thru a mail2news gateway.
No effort was made to verify the identity of the sender.
--------------------------------------------------------

pgp trash troll delete

Hicks, Alan
188 Shady Dale Dr
Lizella, GA 31052
478-935-8132

+Alan Hicks+ <alan@lizella.network> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> In alt.os.linux.slackware, link dared to utter,
> > I am currently in the process of planning a project named strop. In case
> > you couldn't guess it's going to mimic the ports tree from the various
> > BSD's of the world.

> I think you've got an uphill battle here. Other people have done
> something similar and it's just not really caught on. My personal
> feeling is that right now, this is Gentoo's domain, and there's only
> room for one ports-like linux distro.

> Personally I wouldn't use it. I don't like BSD ports much for a variety
> of reasons.

> 1) Many of the ports don't work. They are either un-maintained or
> crippled on certain hardware, meaning you've sorta told some one that
> something will work and then it doesn't. There's no gaurantee that the
> package will do what I want it to do, and too often they are put
> together by people who are only doing it for one system, theirs.
> 2) General cluelessness. One thing I like about Slackware is it leaves
> package management to me, and something like strop just completely
> blows that out of the water. I don't trust random joe noob to build the
> packages I use on my system. If it doesn't come from me, Pat, or the
> people that actually write the software, I don't much trust it.

> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)

> iD8DBQFBP6sklKR45I6cfKARAib6AKCMkHswxgs3xhQbkbDw64 nypkWixgCcCN/m
> pB6TKp5QWpIGmFGLE8we5Gk=
> =n5L4
> -----END PGP SIGNATURE-----

Robert wrote:

> NeoSadist wrote:
>>
>> I would like this project if, and only if, we stay with slackware's
>> system
>> of .SlackBuild scripts. I prefer things the way Pat wanted them,
>> since his ideas work more often then mine and others who have already
>> tried (i.e.
>> linuxpackages, slapt-get, swaret, etc). Even then, what good would
>> this ports system be if we're building from source, since
>> slackware-current usually already has the most current of everything?
>
> I can see it that this would be setup to install pre-built packages or
> build from source like BSD. You could then tailor it to your architect
> like 32/64bit when that becomes a issue.

Why not just start a Slackware 64bit project instead?

--
"The voters have spoken, the bastards ..."

On 2004-09-08, link <link@voidmain.net> wrote:
> I am currently in the process of planning a project named strop. In case
> you couldn't guess it's going to mimic the ports tree from the various
> BSD's of the world.
>
> I am starting to put together the tree now and would like to start coding
> this weekend. However I don't want this to all be in vain.
>
> Please reply with why you would like this project or why you wouldn't.
> There is a better description at sourceforge. go to sourceforge.net and
> search for strop and take a look at the description.
>
> Let me know what all you would like to see improved with the ports trees
> of the BSD's and/or if you would find something like this useful.
>
> -link

Have look at CRUX http://crux.nu/
It has a ports system and a tool "prt-get".
I use it on my iBook

/Jens
--
Slackware | CRUX PPC
window manager improved

link wrote:

> I am currently in the process of planning a project named strop. In case
> you couldn't guess it's going to mimic the ports tree from the various
> BSD's of the world.

maybe you want to have a look at NetBSD's Port System pkgsrc. It already
works on slackware!
http://users.piuha.net/martti/comp/s...slackware.html

good luck!

Stefan Riegel