[Slackbuilds-users] Rebuilding all SBo packages on new system

[Rich Shepard]

I'm preparing a new desktop server/workstation (yes, 64-bit CPU) and need
to rebuild the 316 SBo packages I use on the current, 32-bit, host. Is there
a way to automate this if, for example, I copy the local SBo repository to
the new host?

There is the issue of package dependencies and I'm not seeing how to
efficiently recreate all packages on the new host without having to track
down the dependency hierarchies for each package.

Suggestions and recommendations needed.

Rich
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Jeremy Hansen]

Post by Rich Shepard
I'm preparing a new desktop server/workstation (yes, 64-bit CPU) and need
to rebuild the 316 SBo packages I use on the current, 32-bit, host. Is there
a way to automate this if, for example, I copy the local SBo repository to
the new host?
There is the issue of package dependencies and I'm not seeing how to
efficiently recreate all packages on the new host without having to track
down the dependency hierarchies for each package.
Suggestions and recommendations needed.
Rich

Sounds like David Spencer's slackrepo would be ideal for your situation.

http://idlemoor.github.io/slackrepo/

Jeremy

[David O'Shaughnessy]

Post by Jeremy Hansen
Sounds like David Spencer's slackrepo would be ideal for your situation.
http://idlemoor.github.io/slackrepo/

Jeremy,
  Thank you. I'll get a copy and learn how to use it.
Best regards,
Rich

I would get the list of packages from the old machine:
packages=$(ls /var/log/packages/*_SBo | cut -d'/' -f5 | rev | cut -d-
-f4- | rev)

and then feed that into slackrepo on the new machine:

slackrepo build $packages
(or slackrepo install if you want to install everything).

If there are any build customisations you've made then it would be
worthwhile looking at the HINTFILE system that slackrepo uses. A default
set for slackrepo can be found at:

https://github.com/idlemoor/slackrepo-hints

--
Dave
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slack

[Rich Shepard]

Post by David O'Shaughnessy
packages=$(ls /var/log/packages/*_SBo | cut -d'/' -f5 | rev | cut -d-
-f4- | rev)
slackrepo build $packages
(or slackrepo install if you want to install everything).

Dave,

Finally made time to get the new desktop up and running, and took your
advice to get a list of installed packages.

Post by David O'Shaughnessy
If there are any build customisations you've made then it would be
worthwhile looking at the HINTFILE system that slackrepo uses. A default
https://github.com/idlemoor/slackrepo-hints

I don't see anything in the *.hint files I've checked so far (e.g.,
audacity in Audio). They all seem to point to moving the hint file to a new
directory. This from
<https://github.com/idlemoor/slackrepo-hints/tree/master/ponce/default_hintfiles/14.2>

Am I looking in the wrong directory?

Rich


_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Jeremy Hansen]

Post by Rich Shepard

Post by David O'Shaughnessy
packages=$(ls /var/log/packages/*_SBo | cut -d'/' -f5 | rev | cut -d-
-f4- | rev)
slackrepo build $packages
(or slackrepo install if you want to install everything).

Dave,
Finally made time to get the new desktop up and running, and took your
advice to get a list of installed packages.

Post by David O'Shaughnessy
If there are any build customisations you've made then it would be
worthwhile looking at the HINTFILE system that slackrepo uses. A default
https://github.com/idlemoor/slackrepo-hints

I don't see anything in the *.hint files I've checked so far (e.g.,
audacity in Audio). They all seem to point to moving the hint file to a new
directory. This from
<
https://github.com/idlemoor/slackrepo-hints/tree/master/ponce/default_hintfiles/14.2
Am I looking in the wrong directory?

Those would be the default hintfiles for ponce's repo. You'd want the ones
out of SBo/default-hintfiles

https://github.com/idlemoor/slackrepo-hints/blob/master/SBo/default_hintfiles/

I also have the hintfiles I've created available.

https://github.com/bassmadrigal/slackrepo-hintfiles-14.2

[Rich Shepard]

Post by Jeremy Hansen

Post by Rich Shepard
Am I looking in the wrong directory?

Those would be the default hintfiles for ponce's repo. You'd want the ones
out of SBo/default-hintfiles
https://github.com/idlemoor/slackrepo-hints/blob/master/SBo/default_hintfiles/
I also have the hintfiles I've created available.
https://github.com/bassmadrigal/slackrepo-hintfiles-14.2

Thanks, Jeremy! I was in the wrong directory.

Much appreciated,

Rich
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Jason Graham]

   I'm preparing a new desktop server/workstation (yes, 64-bit
CPU) and need
to rebuild the 316 SBo packages I use on the current, 32-bit, host. Is there
a way to automate this if, for example, I copy the local SBo repository to
the new host?
   There is the issue of package dependencies and I'm not seeing
how to
efficiently recreate all packages on the new host without having to track
down the dependency hierarchies for each package.
   Suggestions and recommendations needed.
Rich
Sounds like David Spencer's slackrepo would be ideal for your situation.
http://idlemoor.github.io/slackrepo/
Jeremy

Agreed. It's a great tool.

Jason