LinuxQuestions.org
Help answer threads with 0 replies.
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 03-24-2020, 09:47 AM   #76
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 229

Original Poster
Rep: Reputation: Disabled

Slacker,

Please run this command after making changes in /etc/attitude/preference file.
Code:
attitude update -s slackware --force
Thanks
 
1 members found this post helpful.
Old 04-05-2020, 03:46 AM   #77
jheengut
Member
 
Registered: Sep 2006
Location: Providence, Moka Mauritius
Distribution: Slackware, Lubuntu
Posts: 336
Blog Entries: 16

Rep: Reputation: 50
Quote:
Originally Posted by linuxxer View Post
Please check project files. Please try it.

I always keep these files up to date.

Suggestions are welcome....

Hi,

what I meant is that if you have a new release, the package name of the source code should change too.


https://sourceforge.net/p/slack-attitude/svn/45/ is the

latest revision but the package name does not reflect that. If you want people to test your program especially those who like to compile their own binary, would download the source code and build everything from scratch similar to how Slackbuilds are designed. There are no associated asc files.



So how do you expect package maintainers to know when/what there is the latest release. Not everyone will come to linuxquestions to check this thread for latest release.


Normally, I would try to automatise everything and there are no such mechanism for a script to detect change in latest revision.



Do not name all your releases 1.0.0. It does not make sense unless you do not want other people to use attitude.
 
Old 04-07-2020, 10:40 AM   #78
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 229

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by jheengut View Post
what I meant is that if you have a new release, the package name of the source code should change too.
It is still alpha release of version 1.0.0.
 
Old 04-07-2020, 10:49 AM   #79
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 229

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by jheengut View Post
So how do you expect package maintainers to know when/what there is the latest release. Not everyone will come to linuxquestions to check this thread for latest release.
As per Knowledge RSS Feed (OR) svn checkout command is sufficient to keep track of changes.

I always keep project-files uptodate.

If any other functionality required to keep track of changes, then please suggest. I will implement it.
 
Old 04-07-2020, 10:55 AM   #80
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 229

Original Poster
Rep: Reputation: Disabled
Slackers,

Now features are freeze for this version (1.0.0). No new feature will be added into the project.

Because it contains sufficient functionality expected from package management tool. It means project is usable.

My main focus is to provide proper and stable functionality.

I have not started working on version 2.0.0.

Thanks
 
Old 04-07-2020, 10:57 AM   #81
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 229

Original Poster
Rep: Reputation: Disabled
@jheengut,

Thanks for suggestions.....
 
Old 04-07-2020, 12:26 PM   #82
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,158

Rep: Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699
Quote:
Originally Posted by linuxxer View Post
It is still alpha release of version 1.0.0.
Quote:
Originally Posted by linuxxer View Post
As per Knowledge RSS Feed (OR) svn checkout command is sufficient to keep track of changes.

I always keep project-files uptodate.

If any other functionality required to keep track of changes, then please suggest. I will implement it.
It's not readily visible on what version you have sitting on your computer and whether you need to grab an update. You could have your various alpha releases as 1.0.0r45, showing this is based on the 45th revision. This allows people to track what they have downloaded and ensures it's easily viewable what version you have and what is available.

But this is just as an outsider who has read your posts (like I do all posts on this subforum). I haven't used it at all, so I can't give anything more detailed. It is just nice to have various releases of a program have separate version numbers to be able to easily differentiate between them.
 
1 members found this post helpful.
Old 04-08-2020, 05:52 AM   #83
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 229

Original Poster
Rep: Reputation: Disabled
Slackers,

Here is an update please check (Slack) Attitude.

Removed symlink nattitude, add enable browse functionality if no argument is provided. Please run:
Code:
attitude

As per suggestion from jheengut Source package version naming is changed. Added alpha$(svn release number).

For those who like to compile using SlackBuild please create symlink.

For example:
Code:
ln -sv attitude-1.0.0alpha46.tar.gz attitude-1.0.0.tar.gz
And run the attitude.SlackBuild script.

Thanks
 
1 members found this post helpful.
Old 04-08-2020, 05:54 AM   #84
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 229

Original Poster
Rep: Reputation: Disabled
@jheengut, @bassmadrigal

Is it right? Please correct...

Thanks for suggesion
 
1 members found this post helpful.
Old 04-08-2020, 08:30 AM   #85
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: AntiX 19
Posts: 6,295
Blog Entries: 21

Rep: Reputation: 3163Reputation: 3163Reputation: 3163Reputation: 3163Reputation: 3163Reputation: 3163Reputation: 3163Reputation: 3163Reputation: 3163Reputation: 3163Reputation: 3163
Usually. Alpha stuff has a ,a , in the number description.
Betas have a, b, in the number description.

It avoids confusion.

Just mentioned by a tester < not on this though >
 
1 members found this post helpful.
Old 04-08-2020, 10:27 AM   #86
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,158

Rep: Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699
Quote:
Originally Posted by linuxxer View Post
@jheengut, @bassmadrigal

Is it right? Please correct...

Thanks for suggesion
This is much better.

And if you want to prevent needing to use a symlink for your SlackBuild, you can switch how it grabs the version helping to automate the SlackBuild without needing to tweak it every time you push an update.

Code:
VERSION=${VERSION:-$(echo $PKGNAM-*.tar.gz | rev | cut -d. -f3- | cut -d- -f1 | rev)}
Then you'd just remove the PKGVERSION variable and switch any calls to it to just $VERSION (unless you really want to keep it, but it is unnecessary with differing package versions).
 
1 members found this post helpful.
Old 04-09-2020, 12:34 PM   #87
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 229

Original Poster
Rep: Reputation: Disabled
@rokytnji, @bassmadrigal

Thanks for the suggestions....
 
Old 04-27-2020, 05:09 PM   #88
jheengut
Member
 
Registered: Sep 2006
Location: Providence, Moka Mauritius
Distribution: Slackware, Lubuntu
Posts: 336
Blog Entries: 16

Rep: Reputation: 50
Thumbs up

Quote:
Originally Posted by linuxxer View Post


Added alpha$(svn release number).

For those who like to compile using SlackBuild please create symlink.

For example:
Code:
ln -sv attitude-1.0.0alpha46.tar.gz attitude-1.0.0.tar.gz
And run the attitude.SlackBuild script.

Thanks



yeah, much better.



all we need now is to submit a proper slackbuilds script.
 
Old 04-27-2020, 05:21 PM   #89
jheengut
Member
 
Registered: Sep 2006
Location: Providence, Moka Mauritius
Distribution: Slackware, Lubuntu
Posts: 336
Blog Entries: 16

Rep: Reputation: 50
Quote:
Originally Posted by bassmadrigal View Post

Code:
VERSION=${VERSION:-$(echo $PKGNAM-*.tar.gz | rev | cut -d. -f3- | cut -d- -f1 | rev)}
Then you'd just remove the PKGVERSION variable and switch any calls to it to just $VERSION (unless you really want to keep it, but it is unnecessary with differing package versions).
Not sure the right place to mention but some packages have their version number on the fourth field, such as ::

Code:
xf86-video-nouveau-blacklist-1.0-noarch-1
the code looks for the version number at the third field starting from the right hand side.

Therefore, to create a package, the program should be able in x86 or x86_64 mode or is it noarch.

Is there a plan to port it to other architectures too?

The first field from the RHS is just the build number o independant of version number.
 
Old 04-27-2020, 08:27 PM   #90
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,158

Rep: Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699Reputation: 5699
Quote:
Originally Posted by jheengut View Post
Not sure the right place to mention but some packages have their version number on the fourth field, such as ::

Code:
xf86-video-nouveau-blacklist-1.0-noarch-1
the code looks for the version number at the third field starting from the right hand side.

Therefore, to create a package, the program should be able in x86 or x86_64 mode or is it noarch.

Is there a plan to port it to other architectures too?

The first field from the RHS is just the build number o independant of version number.
This is only used to find the version number from the filename format commonly seen with source tarballs. The code above uses the rev command to reverse the text, which allows it to work backwards. The program name can have as many dashes as desired because of this. When finished, it reverses everything back so it looks normal.

So if you run the following and remove bits of the command, you'll see what's being accomplished. If source has funky names, it may need to be tweaked.

Code:
echo attitude-1.0.0alpha46.tar.gz | rev | cut -d. -f3- | cut -d- -f1 | rev
You'd need a separate, but similar, line to break down parts of a Slackware package name.
 
  


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 50 01-04-2019 08:36 AM
[SOLVED] Binary package repositories for Slackware linuxxer Slackware 5 08-28-2017 02:10 PM
How to make a Slackware package out of a binary release of an application... Alexvader Slackware 8 11-23-2009 01:04 PM
Package Mangement Ideas fatsheep Linux From Scratch 1 06-10-2007 11:22 PM
MS starting to change his attitude (Open source MS tool) moeminhtun General 15 04-09-2004 10:40 AM

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

All times are GMT -5. The time now is 06:11 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
Open Source Consulting | Domain Registration