LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-01-2018, 05:58 AM   #16
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled

Slacker,

Some issue with new build system.

Thanks
 
Old 12-01-2018, 05:59 AM   #17
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
Slackers,

Some issue with new build system.

Please check.

Thanks
 
Old 12-01-2018, 06:00 AM   #18
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
Slackers,

Dependency for Slackware version 14.2 pcre2-10.32-x86_64-1_SBo.

Thanks
 
Old 12-02-2018, 11:10 PM   #19
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
Slacker,

Few additions.

Please check Wiki.

Thanks
 
Old 12-02-2018, 11:14 PM   #20
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by DaBrze View Post
There is an issue on the slackware64-current. The command 'attitude upgrade-all' forces to update all packages dependent on alsa to the version from the tree /extra/pure-alsa-system/. The system has regular versions of these packages installed, so this update is not needed.
Can you please suggest the functionality (NOT code)?
I think this is issue with package naming. Two different packages (which provide different functions) uses same package name.
Thanks for reply
 
Old 12-03-2018, 02:45 AM   #21
DaBrze
LQ Newbie
 
Registered: Mar 2018
Location: Lodz, PL
Distribution: Slackware-current
Posts: 4

Rep: Reputation: Disabled
The problem may concern the concept of 'attitude'

From the wiki:
Quote:
Concept

This tool uses tag provided as per Slackware package naming convention.
For example: Slackonly repository uses "_slonly" as package tag.
This is used for package source selection during package upgradation.
There is an example of different repositories with the same tag that can not be processed according to this concept:

1) alien-kde / current / latest / x86_64 / (ktown)
2) alien / sbrepos / current / x86_64 /
3) alien / restricted_sbrepos / current / x86_64 /

Another method should be used to distinguish between repos.
 
Old 12-03-2018, 11:50 AM   #22
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,522

Rep: Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267
Quote:
Originally Posted by linuxxer View Post
Can you please suggest the functionality (NOT code)?
I think this is issue with package naming. Two different packages (which provide different functions) uses same package name.
Thanks for reply
It may also be related to subrepo (is that the right name?) preference. alsa-only packages reside in extra/. If extra/ has a higher priority than the main repo (slackware{64}/), then the pulse packages could potentially be replaced with the alsa-only, which may not be desired by the users.

I'm not sure if this is user configurable or something hardcoded into the program (I manually manage my upgrades, so I haven't used this program).

Last edited by bassmadrigal; 12-03-2018 at 11:51 AM.
 
Old 12-04-2018, 10:31 PM   #23
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by DaBrze View Post
There is an example of different repositories with the same tag that can not be processed according to this concept:

1) alien-kde / current / latest / x86_64 / (ktown)
2) alien / sbrepos / current / x86_64 /
3) alien / restricted_sbrepos / current / x86_64 /

Another method should be used to distinguish between repos.
When I say, I am less experience with Slackware. It means I have less experience with package manangement. I uses combination of packages with different repositories. I mostly use packages from Slackware official repository. Few packages from alien and rlworkman plus slackonly repository. And few compiled packages from Slackbuilds.org repository.

I have tried to handle all repositories uniform ways. I don't want to dump any repository specific code.
  1. Slackonly uses _slonly
  2. Rlworkman uses _rlw
  3. And Slackbuild uses _SBo (default)

That is the reason I usee package tag in code to handle the repository.
And as per my knowledge It follows Slackware package naming conventions.

Am I right? Please correct

Thanks for reply
 
Old 12-04-2018, 10:40 PM   #24
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal View Post
It may also be related to subrepo (is that the right name?) preference. alsa-only packages reside in extra/. If extra/ has a higher priority than the main repo (slackware{64}/), then the pulse packages could potentially be replaced with the alsa-only, which may not be desired by the users.

I'm not sure if this is user configurable or something hardcoded into the program (I manually manage my upgrades, so I haven't used this program).
It will unnecessarily complicate the things. I want to keep the things simple.
I know that slackpkg handle such priority for sub-branches.

Insted of MPlayer-20180720-x86_64-1_alsa.txz if it like MPlayer-alsa-20180720-x86_64-1.txz, It will solve the issue.

If I am wrong then please correct...

Thanks for your suggestion.
 
Old 12-04-2018, 11:59 PM   #25
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
Slackers,

Few changes.
--batch option is added.
And attitude-installer is now able to upgrade Slackware core (aaa_*) packages.

Suggestions are welcome....

Thanks
 
Old 12-05-2018, 12:42 AM   #26
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
Slackers,

Few improvement.

Now upgrade-all/sys-upgrade will select kernel-generic, kernel-huge, kernel-modules, kernel-source packages for installation (insted of upgrade).

Please check....

Thanks.
 
Old 12-05-2018, 12:19 PM   #27
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,522

Rep: Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267Reputation: 3267
Quote:
Originally Posted by linuxxer View Post
When I say, I am less experience with Slackware. It means I have less experience with package manangement. I uses combination of packages with different repositories. I mostly use packages from Slackware official repository. Few packages from alien and rlworkman plus slackonly repository. And few compiled packages from Slackbuilds.org repository.

I have tried to handle all repositories uniform ways. I don't want to dump any repository specific code.
  1. Slackonly uses _slonly
  2. Rlworkman uses _rlw
  3. And Slackbuild uses _SBo (default)

That is the reason I usee package tag in code to handle the repository.
And as per my knowledge It follows Slackware package naming conventions.

Am I right? Please correct

Thanks for reply
Tags are good, but they can't be the only thing you use to distinguish between packages. As DaBrze mentioned, each repo can potentially have multiple packages of the same name that are designed for different things. This includes the official repo (with extra/ and testing/ -- both can be used to replace stock packages, and of course, patches/). Alien's SlackBuilds will have multiple packages for different Slackware versions, many times with the exact same name and version. And his ktown can have a current/ and testing/ for those who might be a bit more adventurous.

With the official repo, there needs to be a way to prioritize different folders. Almost all users would want patches/ preferred over slackware64/, and many may want to prefer extra/ or testing/ over the main and/or patches/ directories.

If you don't offer this type of configuration, it may make this program unusable by many Slackers.

Quote:
Originally Posted by linuxxer View Post
It will unnecessarily complicate the things. I want to keep the things simple.
I know that slackpkg handle such priority for sub-branches.

Insted of MPlayer-20180720-x86_64-1_alsa.txz if it like MPlayer-alsa-20180720-x86_64-1.txz, It will solve the issue.

If I am wrong then please correct...

Thanks for your suggestion.
It might complicate things, but IMO, not unnecessarily. As I mentioned above, you need to have a way to prioritize patches/ over slackware64/, and if there's packages in testing/ or extra/ that replace stock packages, people need to have a way to prioritize those over the stock packages.

Renaming those programs would then require you to blacklist all the original ones, which I don't know if you have the ability to blacklist MPlayer and not MPlayer-alsa (slackpkg doesn't currently have this in the stable and Robby has a beta version that does give this functionality).

Keep in mind, these suggestions are just from an outsider looking in since I haven't used the program.
 
Old 12-06-2018, 06:34 AM   #28
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
@bassmadrigal

Thanks for reply.

I tried to follow the Slackware package naming convention while implementing the tool.
Except assigning priority to sub-branch. I will try to implement this functionality as early as possible.

But it is difficult to handle the repositories which doesn't follow the Official Slackware repository structure.
I am talking about sub-branches. And assigning same tag for different repositories.

Please suggest..

Thanks.
 
Old 12-06-2018, 07:04 AM   #29
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: Slackware®
Posts: 141

Original Poster
Rep: Reputation: Disabled
@bassmadrigal

I tried to follow Slackware package naming convention (like tag name) and Official Slackware repository structure.

Please Suggest.....

@slackers

Revert the last changes.
 
Old Yesterday, 04:11 AM   #30
DaBrze
LQ Newbie
 
Registered: Mar 2018
Location: Lodz, PL
Distribution: Slackware-current
Posts: 4

Rep: Reputation: Disabled
Problem with upgrade-all with new kernel:

Quote:
# attitude update
(...)
# attitude --clear tasklist
(...)
# attitude upgrade-all
(...)
Installpkg : kernel-generic-4.19.8-x86_64-1
warning: attitude-installer: kernel-generic-4.19.8-x86_64-1: : Package NOT Found.
error: attitude-installer: attitude_installpkg: kernel-generic-4.19.8-x86_64-1

Last edited by DaBrze; Yesterday at 04:42 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
slackpkg++ : New Package management tool for Slackware (Under Development) linuxxer Slackware 44 10-25-2018 11:02 AM
[SOLVED] Binary package repositories for Slackware linuxxer Slackware 5 08-28-2017 03:10 PM
How to make a Slackware package out of a binary release of an application... Alexvader Slackware 8 11-23-2009 02:04 PM
Package Mangement Ideas fatsheep Linux From Scratch 1 06-11-2007 12:22 AM
MS starting to change his attitude (Open source MS tool) moeminhtun General 15 04-09-2004 11:40 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:56 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration